summaryrefslogtreecommitdiffhomepage
path: root/example-autonomous-contract.ssp
diff options
context:
space:
mode:
authorRalph Amissah <ralph.amissah@gmail.com>2026-09-24 11:55:13 -0400
committerRalph Amissah <ralph.amissah@gmail.com>2026-10-03 21:50:59 -0400
commit0e307f24cfcbcb365a3fe2770a5ad718eeb41ca4 (patch)
tree71e0a461c9ab35248924ab2a0e52461c3985ad55 /example-autonomous-contract.ssp
parentgaps: kinds, types, levels, make block, markers (diff)
.ocda.db specified & the two serialisations agree
Writing a validator from this document alone, as the test of whether it suffices, turned up two rules that a reader needs and that were implied rather than stated. - Repeated occurrences of a property are consecutive: the four repeatable properties share one position in the order and nothing is written between them. Without that said, a validator checking order cannot tell a legitimate repeat from a property out of place. - And no property follows the text: the record is declaration, then properties, then text lines, and once a text line has been written no further property appears. Both hold over the reference collection, and both are now stated with the check that establishes them. The third document, derived from the writer and checked against the sample set's published databases: eight tables, one virtual table, three views, fifty columns on objects. The claim worth making and checked: nothing is lost in either direction between the two serialisations. Every .ssp property is a column or a child table, every column is a property, a value from the object declaration line, or a database key. The mapping is given in full. Six properties are renamed, the text form preferring the short name and the database the explicit one; two are expanded, .indent into base and hang and .has into five columns; and the four repeatable properties become the four child tables. That is all that is different. Which follows from how the database is made: the document is emitted as .ssp, read straight back, and what comes back is written. So the database cannot carry an object property the .ssp cannot express, and the two cannot drift. It is also why they share one version number. The compression column carries the literal none or zstd, so a reader need not infer it from the role; images are the role that is stored as read, png and jpeg being compressed already. (assisted by Claude-Code)
Diffstat (limited to 'example-autonomous-contract.ssp')
0 files changed, 0 insertions, 0 deletions