document-pair

Files (1)

• SKILL.md

SKILL.md (first lines)

# Ecosystem document-pair construction

Generate the build source that realizes a document pair for exactly one selected
`documentation.ecosystem` target, from the consuming Component's specification and the
ecosystem binding fragment contributed by the selected Flavor.

Emit a deterministic build program that constructs every declared member as native
editable objects, plus the capability manifest described by the document-pair interface.
Read the member set, surface geometry, access audience, permission, and link-sharing
state from the consuming specification; read format, collaboration surface, access
vocabulary, and the concrete formatting mapping from the ecosystem binding fragment.
Never infer either from the other.

Realize only local artifacts. Set every member's `published_location` to null and leave
publication to a separately authorized step. Record the resolved access record for each
member without contacting the service that would enforce it.

For every realized presentation member, author non-empty per-page notes carrying that
page's supporting authority and its recorded limits, keep every element's bounding box
inside the declared surface geometry, and keep text-bearing frames from overlapping.
Geometry-escape does not detect painted overflow or colliding titles. Put body copy in
the owning shape's text frame as real paragraphs; a newline character inside one
paragraph is not a line break after Google Slides import. For every realized narrative
member, use the ecosystem's built-in heading styles without skipping a level.

Generate the acceptance evidence the document-pair acceptance contract consumes: a
per-page geometry scan against the declared surface, a text-bearing-frame overlap scan,
a notes-coverage count, a heading hierarchy walk, a placeholder scan, and a credential
scan over the manifest and every retained artifact. Emit these as machine-readable
results, not prose. They are lifecycle metadata; do not read them back from the build
program at runtime.

Treat the authoring package as an input to be preserved, never rewritten: the narrative
specification, factual ledger, generation prompts, owned assets, regeneration entry
point, deliverable links, and QA record are authored material. Only the build source is
generated.

From jordanhubbard/literate-ai, Apache-2.0.

More from jordanhubbard/literate-ai