Capability Atlas

Overview #

A registered gap is a recorded absence, not an oversight: artifacts of this type exist and work in the repository — the accounting counts them from the Git inventory — but the knowledge graph holds no published typed revision for them yet. We record that absence explicitly instead of fabricating a revision after the fact; the gap stays a gap until a revision passes the lifecycle to publication.

created for Talomnia

86

reused from Arcanada and Datarim

42

published (public-sanitized lifecycle)

128

withheld (internal and experimental)

108

total inventory entities

236

Everything created for Talomnia was created in this launch — Talomnia has had no other launch; the reused capabilities come from the Arcanada ecosystem and the Datarim framework.

The catalog does not silently show a subset: for every entity type the table states how many artifacts the knowledge inventory holds and how many are withheld from publication. An artifact stays withheld until it has passed the full lifecycle to public-sanitized status: most withheld skills and roles are Datarim framework definitions imported as graph-grade records without contract-grade payloads, or artifacts carrying no execution evidence from the launch tasks; the rest are drafts and internal artifacts. Publication happens only through lifecycle promotion with evidence at every transition — the visibility gate is never widened to make the catalog look fuller.

Catalog filtered to the neighbours of · show the whole catalog