Skip to content

Support And Maturity

Binder status labels tell readers how much trust to place in a page as a finished teaching surface. They are not protocol importance rankings.

Page Status

Label Reader meaning
final-copy The page has a concrete artifact, worked decode, page-specific ambiguity, source notes, and a bounded observer claim. It is suitable as a style reference.
draft-core-lab The protocol is in Core Lab scope, but the page is not yet promoted to final copy. It may have runnable examples or strong artifacts, while still needing reviewer-grade page depth.
draft-structure-only The page has an atlas-grounded shape and source posture, but lacks enough artifact depth or ambiguity analysis to read as final.
field-note The page teaches a capture or description format slice, usually with a narrower runnable or docs-only boundary.

Runtime Status

A binder page can be useful before a runtime model exists. The status strip on a reader page should say whether a current schoolbus example exists:

  • available means the page points to a runnable docs example or tutorial model that exists in this repository today.
  • not yet available means the page is docs-only for now.
  • docs-only means the repository intentionally records source posture and inspection boundaries without promising a parser or decoder.

Do not include planned API sketches on reader pages. Future implementation ideas belong in issues, plans, or maintainer roadmap surfaces.

Promotion

Promoting a page to final-copy requires the final page checklist. The checklist is a maintainer gate, not prose readers must wade through before learning from an artifact.

Reader Shortcut

For reader trust, status labels should answer one question quickly: "How much can I lean on this page right now?"

  • Use final-copy when the page has a concrete artifact, worked decode, page-specific ambiguity, source-role notes, and bounded observer claims.
  • Use draft-core-lab when the protocol is important and on the Core Lab path, but the page still needs stronger artifact depth, source review, or example support.
  • Use draft-structure-only when the page is mostly a source-grounded map.

Do not promote a page because its protocol is popular. Promote it because the page itself is ready.