Require bound Persona publication receipts
This commit is contained in:
parent
ef26c0753a
commit
09e562e34b
6 changed files with 313 additions and 12 deletions
|
|
@ -1549,7 +1549,27 @@ artifact reads. The stale caller is deleted and aggregate Persona state is
|
|||
candidate speech, local bubble, eligibility, Mind admission, and Bifrost/provider
|
||||
delivery are distinct consequences.
|
||||
|
||||
Prompt signal: Modeling currently requires a durable `statePatch` even when no
|
||||
model change is warranted. That can manufacture persistence merely to satisfy
|
||||
the output contract. The next prompt-contract pass should add a source-grounded
|
||||
`no-state-change` result rather than encouraging ceremonial scratch churn.
|
||||
Prompt signal, corrected after operator review: Modeling must always maintain
|
||||
the live persistent body map. A source pass that confirms existing anatomy
|
||||
still owes a typed freshness/checkpoint witness so Hands can trust the map
|
||||
instead of rediscovering the repo. The prompt improvement is not a
|
||||
`no-state-change` escape hatch; it is sharper language requiring every patch to
|
||||
name changed, confirmed, or invalidated anatomy plus freshness/frontier and
|
||||
semantic-index consequences, so mandatory persistence cannot decay into
|
||||
ceremonial scratch churn.
|
||||
|
||||
## Successful bridge process is not publication
|
||||
|
||||
Eyes inspected Bifrost's actual bridge contract. Discord and Reddit stdout must
|
||||
carry exact action, `ok=true`, destination binding, provider identity/URL,
|
||||
canonical crossing receipt id, and provenance bound to the Persona speech audit,
|
||||
lane, agent, authority, Bifrost identity, and Heimdall capability. Epiphany had
|
||||
accepted exit zero plus arbitrary JSON; Discord even invented a fallback message
|
||||
id. Both mouths now validate the existing Bifrost contract before writing
|
||||
`posted`. Hostile exit-zero `{}` bridges are rejected by native smokes.
|
||||
|
||||
Publication history no longer trusts local artifact `status=posted`. Discord
|
||||
binds the validated receipt into its artifact; both history readers require a
|
||||
receipt whose action, target, provider evidence, crossing id, and audit source id
|
||||
match the artifact. Forged status-only artifacts remain readable local files but
|
||||
cannot increase verified post counts or steer same-target publication pressure.
|
||||
|
|
|
|||
|
|
@ -604,5 +604,19 @@ repo-intake consensus status argument and demoted aggregate Persona status from
|
|||
`ready` to `loaded`. Persona prompts now explicitly separate candidate, bubble,
|
||||
eligibility, Mind admission, and Bifrost/provider delivery ownership. Native
|
||||
negative/smoke checks, 259 library tests, 32 work tests, and all-bin compilation
|
||||
pass. Next repair Modeling's forced-patch prompt pressure and the P0 Discord/
|
||||
Reddit arbitrary-JSON publication receipts found by Eyes and Soul.
|
||||
pass. Operator correction: Modeling's mandatory typed patch is intentional
|
||||
because the live searchable body map is its product; confirmation passes must
|
||||
bank freshness and source-grounded map confidence. Improve the patch vocabulary,
|
||||
do not add a no-state-change escape. Continue the P0 Discord/Reddit arbitrary-
|
||||
JSON publication receipt cut found by Eyes and Soul.
|
||||
|
||||
That P0 cut is complete. Epiphany now validates Bifrost's real Discord/Reddit
|
||||
publication output: exact action/outcome, target, provider id or URL, canonical
|
||||
crossing receipt id, and returned provenance bound to the speech audit and
|
||||
authority inputs. Discord fallback IDs are deleted. Native hostile smokes prove
|
||||
exit-zero `{}` cannot publish. Posted artifacts count as history only when their
|
||||
embedded receipt binds back to the artifact target and audit; forged
|
||||
`status=posted` files do not count. The remaining Bifrost seam is command
|
||||
cardinality: Epiphany inherits a CultMesh command id, so the coordinator must
|
||||
ensure one typed command id per crossing rather than letting multiple posts share
|
||||
one canonical `crossing_<command>` receipt.
|
||||
|
|
|
|||
Reference in a new issue