Draft HACP v0.3 accountable continuation source packet

PUBLICATION-CHECKLIST.md

@@ -8,6 +8,11 @@ Use this before making the repository public.
 - [ ] Confirm README links resolve from the repository root.
 - [ ] Confirm RFC drafts still say HACP is a working draft, not a standard.
 - [ ] Confirm schemas and examples validate against the current draft intent.
+- [ ] For HACP v0.3 candidate material, confirm owner-accepted external proof
+      exists for single-consumer admission, restart readback,
+      claim-before-start failure (reject successor start without durable
+      readback of its accepted claim), ambiguous execution reporting, and
+      expiry/revocation ordering before merging the consumption-contract draft.
 - [ ] Confirm issue templates or discussion settings are ready for public
       review.
 - [ ] Decide whether to publish as a personal repo first or move under an

README.md

@@ -241,15 +241,20 @@ Start here:
   public-safe WITS v0 source packet for task packets, agent reports, human
   decision gates, evidence, stop reasons, transport envelopes, and fixture
   candidates.
+- [docs/source-packets/wits-v0/accountable-continuation-v0.3-draft.md](docs/source-packets/wits-v0/accountable-continuation-v0.3-draft.md):
+  HACP v0.3 candidate source packet for one-successor consumption receipts,
+  fail-closed extension processing, and accountable continuation evidence.
 - [docs/security-boundaries.md](docs/security-boundaries.md): authority,
   report, match-proof, human-decision, digest-domain, and fail-closed
   boundaries.
 - [docs/non-goals.md](docs/non-goals.md): what HACP 0.2 does not define.
 - [docs/review-packet.md](docs/review-packet.md): severity-ordered review
   packet for the 0.2 draft.
 
-HACP 0.2 is not 1.0. It is a draft vocabulary and fixture set for review and
-independent implementation feedback.
+HACP 0.2 is not 1.0. HACP v0.3 material is an even earlier source-packet
+candidate, not a released schema or conformance profile. Both are draft
+vocabulary and fixture material for review and independent implementation
+feedback.
 
 For maturity framing across v0.1 and v0.2, see
 [Stability Lanes](#stability-lanes).
@@ -291,6 +296,13 @@ is reviewable through the 0.2 docs, schemas, profile registry, and fixtures
 listed above. It should not be described as HACP 1.0 or as generally compliant
 until independent implementations and conformance fixtures exist.
 
+## HACP v0.3 Candidate Status
+
+HACP v0.3 candidate material is source-packet-level only. It explores
+accountable continuation, consumption receipts, successor invocation evidence,
+and extension fail-closed behavior. It does not define a released schema,
+runtime, worker launch path, hosted execution surface, or product feature.
+
 ## HACP v0.1 Draft Completeness
 
 The current draft set is minimally reviewable as a v0.1 protocol sketch. It is
@@ -328,8 +340,9 @@ RFC-0008 transport-boundary checks.
 ## Core Invariants
 
 1. Human authority is explicit and cannot be silently delegated away.
-2. Authority comes from an approved task packet, not from the mechanism that
-   transports the packet.
+2. Authority originates with a human approval act and is recorded or referenced
+   by an approved task or authority packet, not by the mechanism that transports
+   the packet.
 3. Manual and automated transport are different layers. Moving a packet does not
    widen the packet's authority.
 4. Closed vocabularies must not silently widen. Profiles may extend them only
@@ -363,6 +376,12 @@ The v0.2 public review surface is the draft chain-of-custody packet:
 - the v0.2 fixtures in [fixtures/happy-path/](fixtures/happy-path/) and
   [fixtures/risk-cases/](fixtures/risk-cases/).
 
+The v0.3 candidate review surface is source-packet material only:
+
+- [docs/source-packets/wits-v0/accountable-continuation-v0.3-draft.md](docs/source-packets/wits-v0/accountable-continuation-v0.3-draft.md);
+- candidate JSON sketches in
+  [docs/source-packets/wits-v0/examples/](docs/source-packets/wits-v0/examples/).
+
 Implementation-specific trial artefacts are not required to review this public
 draft. Future releases may add public evidence bundles, conformance test
 fixtures, and independent implementation reports.

docs/hacp-0.2.md

@@ -54,7 +54,8 @@ authority packet form multiple chains that share an authority origin.
 
 The owner-approved work unit. It defines scope, authority, allowed surfaces,
 forbidden surfaces, stop conditions, verification expectations, and the decision
-boundary. It is the origin of bounded authority.
+boundary. It records or references bounded authority that originates in a
+human approval act; the packet is not an authority source by itself.
 
 HACP 0.2 renames the v0.1 "task packet" concept to "authority packet" to make
 the authority origin explicit. v0.1 task packets and v0.2 authority packets are

docs/source-packets/README.md

@@ -11,6 +11,9 @@ the normal RFC, schema, profile, and fixture process.
 ## Packets
 
 - [WITS v0 HACP source packet](wits-v0-hacp-source-packet.md)
+- [WITS v0 accountable continuation source packet](wits-v0/accountable-continuation-v0.3-draft.md)
+  for HACP v0.3 candidate consumption receipts, successor invocation evidence,
+  and fail-closed continuation boundaries.
 
 ## Boundaries