# External State Protocol — FULL RESEARCH CORPUS Abbreviation: esp Version: v0.3.0 | Generated: unspecified | Files: 1 | Lines: 584 | Payload: 22.1 KiB Source path: /Users/zachshallbetter/Projects/_protocols/external-state-protocol Bundle name: llm-full-docs-esp Corpus Payload SHA-256: 46f1b63d697b0fe5d0953cc5f2c9a758e37750795db5086b71aa5af54b085360 TABLE OF CONTENTS: - ESP-v0.3.0-External-State-Protocol-Definition.md (584 lines, 22.1 KiB) ======================================================================== ======================================================================== ## FILE: ESP-v0.3.0-External-State-Protocol-Definition.md (584 lines, 22.1 KiB) ======================================================================== # External State Protocol (ESP) **Version:** 0.3.0 **Status:** Working canonical candidate - renamed and re-abstracted from ESP v0.2.0 **Reference implementation:** *The Last Undo* Publication Campaign ## Canonical Definition The External State Protocol (ESP) is a versioned protocol for governed movement toward a desired condition whose establishment depends on independent actors or institutions. It defines the required commitments, preserves unresolved conditions as gray, qualifies evidence independently, models relationships separately from transactions, governs execution and authority, exposes the last reversible state before consequential action, records execution through receipts, and carries qualified learning forward across efforts. ESP applies when an actor has agency but not control: the actor can prepare evidence, create value, build relationships, coordinate work, and make commitments, but an external person, organization, market, authority, or institution ultimately determines whether the desired condition becomes established. Influence and relationships are therefore mechanisms inside ESP, not its top-level subject. A campaign is a bounded execution instance of ESP rather than the protocol itself. Persistent relationships, qualified evidence, receipts, and learned paths may survive individual instances and improve the cost, reach, and capability of later efforts. ## Governing Principle > Do not begin with outreach. Begin with the outcome, the evidence, the network, and the value exchange. Outreach is an execution step inside a larger system. ## Purpose ESP addresses situations in which an actor wants an external condition to become true but cannot cause that condition through direct action alone. Examples include publication, adoption, institutional recognition, partnership, market entry, media attention, expert validation, public understanding, community formation, and other outcomes that depend on decisions or actions by independent people and institutions. A campaign is one bounded execution form of ESP: a governed attempt to move an external state. ESP may also be instantiated as an adoption effort, partnership pursuit, standards effort, research-dissemination program, fundraising effort, market-entry effort, or another bounded initiative that would not naturally be called a campaign. ## Protocol Architecture ESP operates across three distinct layers. ### Strategic Layer Defines what must become true, why it matters, what evidence would establish it, which publics and authorities affect it, and which commitments govern promotion. ### Relationship Layer Models the independent people and organizations through which external conditions can change. Relationships are persistent assets with histories, permissions, obligations, trust, and context. They are not equivalent to transactions or contact lists. ### Execution Layer Contains pursuits, introductions, outreach, negotiations, events, publications, partnerships, activations, follow-up, and other concrete work. Execution produces receipts and evidence that feed back into qualification and planning. ## Core Entities The core ESP model contains: - External State Instance - Campaign (optional bounded execution form) - Outcome - Narrative - Claim - Evidence - Person - Organization - Relationship - Connection - Opportunity - Pursuit - Interaction - Commitment - Asset - Story - Event - Signal - Receipt These entities remain distinct. A relationship is not a pursuit. A claim is not evidence. An interaction is not a commitment. Attention is not adoption. A receipt is not the underlying event. ## Commitment Model Every consequential ESP instance objective is expressed through one or more explicit commitments, denoted **K**. Before evaluating readiness for a commitment, the protocol pins the requirements applicable to that commitment: **R(K)** = the required conditions for commitment K. Requirements are not silently rewritten after evidence arrives. For each required property, the assurance state is: - **SATISFIED** — admissible evidence establishes the required property. - **VIOLATED** — admissible evidence establishes that the property is not satisfied. - **GRAY** — admissible evidence establishes neither satisfaction nor violation. Gray is preserved rather than converted into success or failure for convenience. Closure at a commitment is the proportion of required properties that are resolved: **C(K)** = resolved required properties / total required properties. Remaining gray is: **G(K) = 1 - C(K)** A delta compares two measurements made under a compatible pinned contract: **Delta C = C(after) - C(before)** A delta is evidence of measured change on the declared instrument. It is not automatically evidence of desirability, causation, economic value, or general correctness. ## Evidence Qualification ESP does not decide what evidence means merely because the campaign collected it. Evidence qualification is delegated to the Evidence Qualification Protocol (EQP). ESP may collect, organize, route, preserve, and reference evidence. EQP determines whether that evidence is admissible and what it establishes relative to the pinned requirement. This prevents semantic inflation such as: - attention becoming demand; - an introduction becoming a relationship; - a positive response becoming a commitment; - founder testimony becoming independent validation; - a publication becoming adoption; - an internal result becoming an external fact; - absence of evidence becoming zero. ## Execution Execution follows the Iterative Evidence-Pinned Execution (IEPE) pattern: **Pinned protocol -> Ready work -> Execution -> Receipt -> Evidence qualification -> State update -> Next Ready work** Work enters execution only when its prerequisites and authority are satisfied. Execution produces receipts. Receipts preserve what happened, under which protocol and authority, against which candidate or pursuit, and with what resulting evidence. The receipt does not automatically prove the campaign claim. It makes the execution state inspectable. ## Initialization The instance bootstrap function is provided by the FPB initialization model. Initialization establishes the instance identity, protocol version, objective, owner, authorities, initial evidence, known constraints, relationship context, and first Ready work. Instance initialization does not imply campaign readiness for external promotion. ## Relationship Model Relationships persist across campaigns. Canonical relationship states are: **Unknown -> Researched -> Mapped -> Contactable -> Introduced -> Responsive -> Developing -> Active -> Trusted -> Partner -> Advocate** Additional states include **Dormant** and **Closed**. A relationship record may contain: - professional role and organization; - relevant areas of work; - recent relevant activity; - why the person or organization matters; - relationship origin; - introducer or connection path; - substantive interaction history; - commitments and obligations; - observed professional preferences; - current legitimate reason for contact; - next justified action; - unresolved obligations; - last meaningful interaction; - explicit boundaries or Do Not Ask conditions. Relationship intelligence is limited to legitimate professional context. ESP does not authorize invasive personal profiling. ## Relationship Readiness Relationship readiness is evaluated using a ledger of: - Trust - Utility - Familiarity - Reciprocity - Permission These are readiness dimensions, not debts owed by the other party. No relationship state creates an entitlement to access, favorable coverage, endorsement, participation, or action. ## Connection Paths ESP distinguishes: - Direct - First-degree - Second-degree - Institutional - Cold A cold approach should not be selected before checking whether a legitimate warmer path exists. Warmth must not be manufactured or falsely implied. ## Introduction Protocol An introduction is qualified when: 1. the target has a legitimate reason to care; 2. the introducer genuinely understands the relevant context; 3. the proposition can be represented accurately in a small amount of language; and 4. the introducer can decline without pressure. An introduction is not a successful pursuit. It changes the relationship state and may create permission for a subsequent action. ## Pursuit Model A pursuit is the smallest strategic external effort directed toward a defined opportunity. Canonical pursuit states are: **Candidate -> Qualified -> Prepared -> Approached -> Engaged -> Evaluating -> Negotiating -> Committed -> Preparing -> Executing -> Completed/Published -> Follow-up -> Continued** Terminal states include: - Declined - Deferred - No Response - Withdrawn - Inappropriate - Conflict - Closed Each pursuit should have a defined objective, target, relationship path, evidence basis, value proposition, smallest appropriate ask, authority, next state, and stopping condition. ## Outreach Brief Before outreach, ESP requires answers to: - Why this person or organization? - Why this opportunity? - Why now? - Why should they care? - What is the smallest appropriate ask? - What evidence supports the proposition? - What relationship or introduction path exists? - What concerns or conflicts are foreseeable? - What state should a successful interaction produce? Outreach without these answers is not Ready work. ## Value Exchange ESP models influence as legitimate exchange among independent actors, not as extraction. Different participants possess different scarce assets. A journalist may hold editorial authority and audience. A publisher may hold distribution, capital, production capability, and market access. An expert may hold professional authority. A participant may hold experience, legitimacy, access, or a community. The campaign may hold information, evidence, access, novelty, coordination, useful artifacts, or opportunities for participation. The system asks what each participant legitimately gains from the interaction. Professional value may be invested before an ask through useful information, introductions, sources, logistical help, responsiveness, access, or other legitimate assistance. Such investment must not become disguised payment for favorable independent treatment. ## Strategic Artifacts Every substantial campaign may maintain seven core planning artifacts. ### Outcome Brief Defines what must actually become different in the world. Vanity metrics are excluded unless they are themselves the desired external condition. ### Public Map Maps affected groups, overlapping identities, authorities, intermediaries, beliefs, motivations, resistance, and channels. ### Reality Ledger For each desired belief or claim, records what observable evidence makes the proposition defensible. Where necessary evidence does not exist, communications work stops and operational work begins. ### Narrative Position Records current reputation, desired reputation, and the sequence of credible transitions between them. ### Attention Ladder Defines a sequence in which one event, artifact, reaction, or signal creates conditions for the next. Audience reaction can become evidence for later stages, but attention remains evidence only of attention unless further qualification is available. ### Access Strategy Evaluates opportunities according to audience, authority, prestige, timing, saturation, exclusivity, risk, conditions, and opportunity cost. Saying no or later is a legitimate strategic action. ### Campaign Ledger Records what happened, who responded, which intermediary moved, which language propagated, unexpected interpretations, secondary effects, failures, receipts, and repeat/avoid decisions. ## Propagation Map ESP distinguishes reach from propagation. A propagation map records causal or plausibly linked movement of an idea through actors and channels, for example: **researcher -> journalist -> executive -> newsletter -> community -> podcast -> search** The system records paths where evidence permits them. It does not convert coincident mentions into causal propagation. ## Authority Authority remains explicit throughout the protocol. Relevant authority classes include: - execution authority; - qualification authority; - relationship authority; - financial authority; - contract authority; - commitment authority; - promotion authority; - owner authority. Possessing one class does not imply possession of another. A person authorized to execute an outreach action may not be authorized to change the campaign contract. A person qualified to evaluate evidence may not be authorized to promote the campaign. A relationship owner may not be authorized to make financial commitments. No consequential decision is allowed to become ownerless. ## Last Undo Every consequential action should expose its last reversible state. Before crossing a commitment boundary, the system identifies: - the current reversible state; - the commitment event; - the required conditions; - the available evidence; - unresolved gray; - applicable authority; - the consequence after commitment; - the fallback or refusal path. Where reversibility is a gradient rather than a natural discontinuity, the campaign pins the threshold that defines the commitment boundary. ## External State Lifecycle The generalized lifecycle is: **Bootstrap -> Discover -> Define -> Contract -> Baseline -> Map -> Prepare -> Execute -> Observe -> Qualify -> Decide -> Commit -> Promote -> Measure -> Learn -> Continue** The lifecycle is not necessarily a one-pass pipeline. Campaigns may return to earlier states when evidence changes, requirements are legitimately versioned, a pursuit fails, or a new external condition appears. ## Nested Instances and Campaigns ESP instances may contain nested instances or campaigns. A publication campaign may contain an agent campaign, a publisher campaign, a research campaign, a media campaign, a speaking campaign, and a launch campaign. Each nested instance has its own commitments and evidence while inheriting only the parent context explicitly allowed by the protocol. Success in a child instance does not silently satisfy a parent commitment. ## Attention and Adoption Attention is evidence only of attention. Coverage is evidence of coverage. A meeting is evidence that a meeting occurred. An endorsement is evidence of an endorsement. A sale is evidence of a sale. Adoption, belief, reputation change, institutional acceptance, and commercial demand require their own evidence. This distinction is fundamental to ESP. ## Negotiation and Commitments Material negotiations use a commitment register containing, as applicable: - parties; - deliverables; - dates; - format; - permissions; - rights; - financial terms; - embargoes; - exclusivity; - logistics; - cancellation; - dependencies; - review rights; - unresolved conditions. Paid, sponsored, controlled, affiliated, and independent activity must remain distinguishable. ## Onboarding Once a pursuit becomes committed, the problem changes from persuasion to execution friction. Onboarding provides role-appropriate information, assets, access, logistics, deadlines, expectations, permissions, restrictions, and responsible contacts. The system should provide no more information than is useful and appropriate to the participant's role. ## Follow-Through After execution, ESP requires: 1. verify obligations; 2. deliver promised materials; 3. resolve mistakes; 4. acknowledge the participant appropriately; 5. capture receipts and artifacts; 6. update the relationship state; 7. update the campaign evidence; 8. map newly legitimate connections; 9. identify the next justified action; 10. stop selling until another legitimate reason to engage exists. Publication or execution is not the end of a relationship. It creates a new relationship state. ## Network Maintenance Relationships are maintained through legitimate value and relevant events, not empty periodic contact. The network is a persistent campaign asset, but people are not inventory. Records exist to preserve context, promises, permission, and professional continuity. ## War Room A campaign operating view should expose: - Outcomes - Narratives - Evidence - Priority publics - Relationship graph - Active pursuits - Attention ladder - Commitments - Signals - Risks - Next moves The purpose is to make campaign state inspectable rather than to maximize activity. ## Measurement ESP distinguishes at least five measurement families: ### Reach Who encountered the work? ### Authority Which credible or consequential actors engaged with it? ### Adoption Who actually used, accepted, purchased, implemented, cited, taught, or otherwise adopted it? ### Propagation How did the idea move between actors and channels? ### Position Did the external understanding or standing of the person, work, organization, or initiative change in the intended direction? Metrics must remain attached to the claim they can actually establish. ## Formalization Boundary ESP structures judgment without claiming to eliminate it. The protocol formalizes states, evidence requirements, authority, relationships, commitments, receipts, and transitions where formalization improves accountability or recomputability. It does not claim that narrative quality, editorial judgment, cultural significance, human trust, strategic taste, or relationship meaning can always be reduced to deterministic predicates. The formal system must remain answerable to reality. ## Governance ESP requires: - no fabrication or material distortion; - disclosure of paid, sponsored, controlled, or affiliated activity where relevant; - preservation of journalistic and expert independence; - no fake-neutral research or manufactured third-party authority; - non-invasive relationship intelligence; - no coercive debt or manufactured obligation; - participant understanding appropriate to the interaction; - provenance for material evidence; - receipts for consequential execution; - explicit authority for consequential commitments. The protocol does not authorize deception merely because deception might improve campaign performance. ## Persistent Memory ESP instance results feed a persistent relationship and knowledge system. The system preserves: - relationship history; - qualified evidence; - interaction receipts; - failed approaches; - successful paths; - commitments; - useful assets; - language that propagated; - channel behavior; - authority patterns; - timing effects; - unresolved questions. The purpose is compounding capability, not indiscriminate data accumulation. Each ESP instance should reduce the cost of correctly orienting the next campaign without allowing stale context to become current truth automatically. ## Versioning ESP is versioned. An ESP instance pins the protocol version under which its commitments, evidence rules, and lifecycle decisions were made. Protocol changes require an explicit review radius. Clarifications that do not change semantics may receive patch releases. New backward-compatible capabilities receive minor releases. Breaking changes to commitment semantics, assurance states, authority, evidence qualification, or lifecycle meaning require a major version. A protocol upgrade does not silently rewrite historical campaign state. ## Protocol Learning ESP itself is subject to evidence. ESP instances can reveal that a relationship state is missing, a pursuit transition is ambiguous, a metric is misleading, an authority boundary is incomplete, or a planning artifact does not predict useful action. Such findings become protocol-change candidates. The protocol improves by the same principle it imposes on instances: findings outrank the framework. ## Conformance An implementation conforms to ESP when it preserves the protocol's semantic boundaries even if its software, database, interface, terminology presentation, or workflow differs. At minimum, a conforming implementation must preserve: - explicit outcomes and commitments; - pinned requirements; - SATISFIED / VIOLATED / GRAY semantics; - evidence provenance and qualification boundaries; - separation of relationships from pursuits; - explicit authority; - governed commitment transitions; - receipts for consequential execution; - last-undo awareness; - persistent cross-instance learning; - version pinning. A system that merely stores contacts and outreach sequences is not an ESP implementation. ## Relationship to the Supporting Protocols ESP is the human-network and external-condition layer of a larger architecture. **FPB** initializes bounded instance state. **Distance from Gray** supplies the commitment-centered assurance model and measurement vocabulary. **EQP** qualifies evidence. **IEPE** governs evidence-pinned execution. **The Formalist** supplies the boundary discipline for deciding what should and should not be formalized. **Authority governance** determines who may execute, qualify, commit, promote, spend, contract, and override. **The Last Undo principle** requires consequential actions to expose the final reversible state before commitment. Together, these form a system for governed movement from an uncertain present state toward an externally established condition without hiding uncertainty, conflating evidence with assertion, or allowing execution to outrun authority. ## Reference Implementation: The Last Undo Publication Campaign *The Last Undo* publication campaign is a reference implementation of ESP, not part of the protocol's domain definition. Its campaign commitments include publisher readiness, literary-agent commitment, publisher commitment, public-launch commitment, and the eventual bestseller attempt. The reference implementation demonstrates how the generalized protocol can be instantiated for publishing while leaving ESP applicable to products, organizations, partnerships, institutional adoption, research programs, public initiatives, and other domains. --- **Canonical short form** > ESP governs how an actor moves toward an external condition that depends on independent people or institutions. It pins the desired commitments, preserves gray, qualifies evidence independently, models relationships separately from transactions, governs execution and authority, records consequential actions through receipts, exposes the last undo before commitment, and carries qualified learning forward so later efforts begin with more capability than the last.