<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sisudoc-abstraction-format/example-autonomous-contract.ssp, branch claude-markdown</title>
<subtitle>SiSU Spine: specs</subtitle>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-abstraction-format/'/>
<entry>
<title>format 2.1: a poem is a container, cited as the range of its verses</title>
<updated>2026-09-29T18:02:30+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-09-29T18:02:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-abstraction-format/commit/?id=0cbfcb1de61217fc0a9d5d973d32f3c14a7648ac'/>
<id>0cbfcb1de61217fc0a9d5d973d32f3c14a7648ac</id>
<content type='text'>
.ocn_range, the first and last ocn of what a container holds, as one
.ssp property and two .ocda.db columns. A poem is the one container:
its verses are the citable units and the poem is not. It now comes
before its first verse, carries ocn 0 and no identifier, and states
the range, where it came after its last verse carrying that verse's
ocn and identifier, so that one number named two objects: 48 such
pairs in the reference collection, none now.

So the model can now say that a non-zero ocn is unique within a
document, and does, keeping the older rule for artefacts written
before 2.1. A minor bump: an addition, a poem was never rendered and
has no text, the verses are unchanged, and a 2.0 reader reads a 2.1
file.

The property-count table is recounted over the regenerated reference
set, the method first checked against the old set, which it
reproduces. The one new endnote, a note in a poem's last verse now
gathered, accounts for the other moved counts; the poems' segment
names account for .segment_html_is and .segment_epub_is. Neither
example holds a poem, so each changed by its version line alone.

(assisted by Claude-Code)

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
.ocn_range, the first and last ocn of what a container holds, as one
.ssp property and two .ocda.db columns. A poem is the one container:
its verses are the citable units and the poem is not. It now comes
before its first verse, carries ocn 0 and no identifier, and states
the range, where it came after its last verse carrying that verse's
ocn and identifier, so that one number named two objects: 48 such
pairs in the reference collection, none now.

So the model can now say that a non-zero ocn is unique within a
document, and does, keeping the older rule for artefacts written
before 2.1. A minor bump: an addition, a poem was never rendered and
has no text, the verses are unchanged, and a 2.0 reader reads a 2.1
file.

The property-count table is recounted over the regenerated reference
set, the method first checked against the old set, which it
reproduces. The one new endnote, a note in a poem's last verse now
gathered, accounts for the other moved counts; the poems' segment
names account for .segment_html_is and .segment_epub_is. Neither
example holds a poem, so each changed by its version line alone.

(assisted by Claude-Code)

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>format 2.0: the model and the .ssp, specified afresh</title>
<updated>2026-09-24T15:07:13+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-09-24T15:07:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-abstraction-format/commit/?id=93370e9ccb0fee20d11db3946fb79332a6c7a1ba'/>
<id>93370e9ccb0fee20d11db3946fb79332a6c7a1ba</id>
<content type='text'>
The previous specification described format 0.1 and was two major
versions behind: four properties were emitted and undocumented, two
of them on nearly every object; four were documented and never
emitted; and it mentioned neither the version banner nor the @source
block.  Both worked examples were 0.22.0 output.  Discarded rather
than revised.

Derived from the emitter, sisudoc/ocda/abstraction/ssp.d, whose
sspObjectRecord is the single definition of what an object looks
like, and checked against the 36 document reference set.  Where the
two could differ the emitter is normative and the specification is
wrong; it says so.

Three documents where there was one, so that the model is described
once rather than in each format specification:

  ocda-model.md                    the model: what an object is, the
                                   citation number, structure,
                                   sections, segments, digests.  The
                                   part both serialisations share
  ssp-format-specification.md      the model written as text
  ocda-db-format-specification.md  the model written as sqlite, to
                                   come

The naming follows the three levels: ocda names the model,
abstraction names the pipeline stage, and .ssp and .ocda.db name the
two serialisations.  A thing is named for the level it belongs to,
which is why this file is ssp-format-specification.md and not
ocda-format-specification.md: it specifies one serialisation, not the
model.

What the mechanical derivation found that reading would not have:
the property set is 42 and not the 39 the corpus exercises, three
being emitted under conditions no sample document meets; property
order is fixed, and provably so, no object of 56,882 emitting one out
of the emitter order; @meta defines 43 keys where the collection uses
28; and a heading declaration line carries its level and identifier,
where every other kind carries the identifier as a property.

The specification now also states the version and the policy that
governs it, which the old file had no notion of, and separates
conformance into what a reader must do, should do, and what a writer
must do.  The single "should" is that a reader should report what it
ignored: without it, silence cannot be told from understanding.

Both worked examples regenerated from spine 0.25.0.  The excerpt
carries one complete object embedding an image, so the .image record
and the image marker in the object text can be read against each
other.

The name .ssp is recorded: it belongs to the .sst, .ssm, .ssi family
and stands loosely for sisu peg or sisu parsable, .ssa for sisu
abstraction having been thought taken by other projects.

(assisted by Claude-Code)

Co-Authored-By: Claude Opus 5 (1M context) &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The previous specification described format 0.1 and was two major
versions behind: four properties were emitted and undocumented, two
of them on nearly every object; four were documented and never
emitted; and it mentioned neither the version banner nor the @source
block.  Both worked examples were 0.22.0 output.  Discarded rather
than revised.

Derived from the emitter, sisudoc/ocda/abstraction/ssp.d, whose
sspObjectRecord is the single definition of what an object looks
like, and checked against the 36 document reference set.  Where the
two could differ the emitter is normative and the specification is
wrong; it says so.

Three documents where there was one, so that the model is described
once rather than in each format specification:

  ocda-model.md                    the model: what an object is, the
                                   citation number, structure,
                                   sections, segments, digests.  The
                                   part both serialisations share
  ssp-format-specification.md      the model written as text
  ocda-db-format-specification.md  the model written as sqlite, to
                                   come

The naming follows the three levels: ocda names the model,
abstraction names the pipeline stage, and .ssp and .ocda.db name the
two serialisations.  A thing is named for the level it belongs to,
which is why this file is ssp-format-specification.md and not
ocda-format-specification.md: it specifies one serialisation, not the
model.

What the mechanical derivation found that reading would not have:
the property set is 42 and not the 39 the corpus exercises, three
being emitted under conditions no sample document meets; property
order is fixed, and provably so, no object of 56,882 emitting one out
of the emitter order; @meta defines 43 keys where the collection uses
28; and a heading declaration line carries its level and identifier,
where every other kind carries the identifier as a property.

The specification now also states the version and the policy that
governs it, which the old file had no notion of, and separates
conformance into what a reader must do, should do, and what a writer
must do.  The single "should" is that a reader should report what it
ignored: without it, silence cannot be told from understanding.

Both worked examples regenerated from spine 0.25.0.  The excerpt
carries one complete object embedding an image, so the .image record
and the image marker in the object text can be read against each
other.

The name .ssp is recorded: it belongs to the .sst, .ssm, .ssi family
and stands loosely for sisu peg or sisu parsable, .ssa for sisu
abstraction having been thought taken by other projects.

(assisted by Claude-Code)

Co-Authored-By: Claude Opus 5 (1M context) &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>spec: .parent emission rule, regenerate the worked example</title>
<updated>2026-09-03T00:26:44+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-09-03T00:26:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-abstraction-format/commit/?id=f934da74b13168782332a1283e32f88f7a0f32dd'/>
<id>f934da74b13168782332a1283e32f88f7a0f32dd</id>
<content type='text'>
.parent is no longer "omit when zero". spine emits it for every
object, 0 included, except the :A~ document root (no parent) and the
entries of the generated @toc section (furniture, placed by their
.indent level; the toc heading itself keeps .parent: 1). A missing
.parent must not be read as 0.

- omission table row and a new paragraph under Properties
- example-autonomous-contract.ssp regenerated from spine 0.22.0,
  which also picks up the ancestors / dom_status / last_descendant /
  parent_lev fixes made in spine since 2026-08-27, and the corrected
  .ocn_off on paragraph objects

example-wealth-of-networks.ssp is a hand-elided excerpt and has not
been regenerated; its verbatim lines predate these changes.

(assisted by Claude-Code)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
.parent is no longer "omit when zero". spine emits it for every
object, 0 included, except the :A~ document root (no parent) and the
entries of the generated @toc section (furniture, placed by their
.indent level; the toc heading itself keeps .parent: 1). A missing
.parent must not be read as 0.

- omission table row and a new paragraph under Properties
- example-autonomous-contract.ssp regenerated from spine 0.22.0,
  which also picks up the ancestors / dom_status / last_descendant /
  parent_lev fixes made in spine since 2026-08-27, and the corrected
  .ocn_off on paragraph objects

example-wealth-of-networks.ssp is a hand-elided excerpt and has not
been regenerated; its verbatim lines predate these changes.

(assisted by Claude-Code)
</pre>
</div>
</content>
</entry>
<entry>
<title>examples: real spine output in place of the hand-written ones</title>
<updated>2026-08-27T18:01:16+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-08-27T18:00:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-abstraction-format/commit/?id=047ec2a6f7eecae8f08f1ea609c3f25aa13966aa'/>
<id>047ec2a6f7eecae8f08f1ea609c3f25aa13966aa</id>
<content type='text'>
Both example files said so in their own headers: "Hand-crafted
example showing what the serialized abstraction would look like",
with illustrative OCNs. They predated several format changes and
neither showed an object embedding an image.

example-autonomous-contract.ssp is now spine's output for that
sample document, complete and unedited but for the comment lines
naming the command that regenerates it.

example-wealth-of-networks.ssp is an excerpt of spine's output for
that document, the whole being some 19,500 lines: verbatim lines
with marked elisions, keeping the @meta / @make / @doc_has
preamble, the @head section, and body objects [95] to [99], among
them [97], which embeds an image and so carries an .image record.

Both parse: ssp-reader --tree and --images read them, the latter
reporting the image record of [97] against the digest the pod's
digests.txt gives for won_benkler_2_1.png.

README: the two files described separately (complete / excerpt),
and the quickstart names the flags that actually write a .ssp.

Carries with it the git.sisudoc.org namespace corrections to the
README links that were already staged in the working tree.

(assisted by Claude-Code)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Both example files said so in their own headers: "Hand-crafted
example showing what the serialized abstraction would look like",
with illustrative OCNs. They predated several format changes and
neither showed an object embedding an image.

example-autonomous-contract.ssp is now spine's output for that
sample document, complete and unedited but for the comment lines
naming the command that regenerates it.

example-wealth-of-networks.ssp is an excerpt of spine's output for
that document, the whole being some 19,500 lines: verbatim lines
with marked elisions, keeping the @meta / @make / @doc_has
preamble, the @head section, and body objects [95] to [99], among
them [97], which embeds an image and so carries an .image record.

Both parse: ssp-reader --tree and --images read them, the latter
reporting the image record of [97] against the digest the pod's
digests.txt gives for won_benkler_2_1.png.

README: the two files described separately (complete / excerpt),
and the quickstart names the flags that actually write a .ssp.

Carries with it the git.sisudoc.org namespace corrections to the
README links that were already staged in the working tree.

(assisted by Claude-Code)
</pre>
</div>
</content>
</entry>
<entry>
<title>rename .sda references and files to .ssp</title>
<updated>2026-04-21T18:16:00+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-04-21T18:16:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-abstraction-format/commit/?id=bc2d3f1e2a2793c7a55d1671a2ddd344780136d2'/>
<id>bc2d3f1e2a2793c7a55d1671a2ddd344780136d2</id>
<content type='text'>
Rename file extension from .sda to .ssp throughout the
format specification and example files.

- example-autonomous-contract.sda -&gt; .ssp
- example-wealth-of-networks.sda -&gt; .ssp
- format-specification.md: all .sda references updated

Co-Authored-By: Anthropic Claude Opus 4.6 (1M context)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Rename file extension from .sda to .ssp throughout the
format specification and example files.

- example-autonomous-contract.sda -&gt; .ssp
- example-wealth-of-networks.sda -&gt; .ssp
- format-specification.md: all .sda references updated

Co-Authored-By: Anthropic Claude Opus 4.6 (1M context)
</pre>
</div>
</content>
</entry>
</feed>
