Documentation

We turn strategy into a complete identity, then package the standards, assets, and implementation tools that keep it coherent in real work.

Documentation for BrandBuilder 3.0.1. Official release and exact skill asset.

Explore each part of the system below.

How the system fits together

These summaries express the same relationships visually and in visible text, so they remain complete without scripts, animation, color, or graphics.

Documentation ownership

Each surface has one job and an explicit boundary.

1. Main manualOwns system architecture, operating modes, contracts, verification, versions, and extension procedures.
2. Hosted brand referenceOwns the current approved brand presentation, assets, bindings, affiliation, and generated version summary.
3. Bundled implementation contractOwns exact delivered paths, version pins, checks, recovery bytes, and offline implementation rules.

Operating modes

The requested outcome determines the mode before files change.

1. AuthorChange governed sources and templates, then regenerate and verify.
2. ImplementationConsume exact generated contracts without creating parallel authority.
3. AuditInspect and report conformance evidence without silently changing the delivery.

Capability improvement loop

Reusable gaps move upstream only through explicit authorization and versioned adoption.

1. 1. Consumer needIdentify a reproducible requirement that the current shared contract does not satisfy.
2. 2. Local gap recordCapture the need, semantic concept, and evidence without changing shared authority.
3. 3. Authorized upstream changeUpdate the owning canon, recipe, or adapter only after human authorization.
4. 4. Versioned adoptionPublish, verify, and let consumers deliberately adopt the exact new version.