Development record
The scribe protocol, the definition's Delivery section, and the changelog entry claim record_schema judges a scribe-emitted reading or disposition record the moment it is committed and that the validation path exists today; on this base no reading or disposition schema or store exists (spc-58 is open), so record_schema refuses the directory as an undeclared bucket and a malformed record is indistinguishable from a well-formed one. The dependency on spc-58 must be stated in all three places.
issueresolvedmajoriss-2608300143316805
The scribe protocol, the definition's Delivery section, and the changelog entry claim record_schema judges a scribe-emitted reading or disposition record the moment it is committed and that the validation path exists today; on this base no reading or disposition schema or store exists (spc-58 is open), so record_schema refuses the directory as an undeclared bucket and a malformed record is indistinguishable from a well-formed one. The dependency on spc-58 must be stated in all three places.
Frontmatter
| id | iss-2608300143316805 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2608300143316805-scribe-protocol-claims-a-validation-path.md
open on GitHub ↗ · commit history ↗
mentions1
- spc-58Reading records and disposition records: two acts, two writes