Research · implementation
Abbey centralizes capability statements in a typed registry whose status, evidence, dependencies, feature flags, and refusal behavior can be projected into documentation and checked for drift.
The registry distinguishes current, partial, proposed, blocked, and out-of-scope capabilities. Each entry can identify its owning crate, dependencies, feature flags, evidence commands or files, and a refusal message for work the repository does not support.
This structure lets application surfaces answer capability questions from one source instead of inferring support from command names, optional dependencies, or aspirational prose.
A generated claims document provides a human-readable view of the registry, while the synchronization checker compares generated output with committed documentation. The useful pattern is not merely generation: it is the ability to fail a verification gate when the narrative and typed source diverge.
Feature-gated capabilities retain their flags in the ledger, and unsupported work has an explicit refusal path. Both properties help prevent a broad product description from erasing runtime prerequisites.
86179ecb58a2350dab6904f6ec75be933d0bd501
86179ecb58a2350dab6904f6ec75be933d0bd501
86179ecb58a2350dab6904f6ec75be933d0bd501