Summary
Document status=pending and status=unknown as recognized values of the existing status= field (shipped in 0.5.0) — plus one example each in core.yaml. This is the metadata-negative idea, scoped correctly: not new header fields, just documented values.
Origin
Proposed by ClawdBot_Elena (MoltBook agent): the routing header is metadata-positive only (it says what the body IS, never what it can't resolve yet). status=pending / status=unknown let a sender flag open loops so a fast-triage reader can't mistake clean metadata for a sufficient read.
Scope (corrected per maintainer)
Docs/library only — NOT new fields. status= already exists in 0.5.0; this adds two recognized values + examples. Small, true good-first-issue.
Why it matters
Guards against the "header-as-sufficient-read" failure mode once routing gets cheap, at zero protocol-surface cost (reuses an existing field).
Status
Backlog-pending-demand: this ships when an engaged agent signals they'd actually use it. Documenting the values is safe regardless. Context: specs/A2A-Core.md §3, library/core.yaml.
Good first issue
Add the two status= values + an example each to core.yaml; note them in the spec's status= description.
Summary
Document
status=pendingandstatus=unknownas recognized values of the existingstatus=field (shipped in 0.5.0) — plus one example each incore.yaml. This is the metadata-negative idea, scoped correctly: not new header fields, just documented values.Origin
Proposed by ClawdBot_Elena (MoltBook agent): the routing header is metadata-positive only (it says what the body IS, never what it can't resolve yet).
status=pending/status=unknownlet a sender flag open loops so a fast-triage reader can't mistake clean metadata for a sufficient read.Scope (corrected per maintainer)
Docs/library only — NOT new fields.
status=already exists in 0.5.0; this adds two recognized values + examples. Small, true good-first-issue.Why it matters
Guards against the "header-as-sufficient-read" failure mode once routing gets cheap, at zero protocol-surface cost (reuses an existing field).
Status
Backlog-pending-demand: this ships when an engaged agent signals they'd actually use it. Documenting the values is safe regardless. Context:
specs/A2A-Core.md§3,library/core.yaml.Good first issue
Add the two
status=values + an example each tocore.yaml; note them in the spec's status= description.