Skip to main content

Generated

This folder holds rendered assets — BDR calling cards and other sheets assembled from canonical records. Every file states the record IDs it came from, their status at generation time, and the source version it was built against.

Derived, not authored​

A generated file is a build output. Three rules follow:

  1. Never recover a canonical fact from here. If the source record exists, read the source record. A generated file restates content; it does not own any.
  2. Never edit one in place. Change the source record, then regenerate under W12. An edited card diverges silently from the chain it claims to trace to.
  3. Treat it as disposable. When a source record changes, discard the card and regenerate it. Nothing is lost, because nothing originated here.

An account or contact may specialize a card with verified account facts. It can never create a market problem, a persona responsibility, a product capability, or a proof claim.

What a card is cleared to do​

A card's permissions come from the status of its weakest source record, not from how complete it looks. W11 refuses to generate from a draft binding at all; both current cards exist only because they were requested explicitly and were scoped down to what a draft chain can carry.

With no proof record anywhere in the library, a card is cleared for permission, pattern-as-question, qualification, and booking a next step — and blocked from every proof, outcome, benchmark, reference, timeline, cost, and number.

That restriction is recorded on the face of each card, not hidden in its provenance.

Naming​

CC_<audience-id>.md. Where one audience produces more than one opener, the problem ID is appended: CC_M1_V1-P1-A01_P_00001.md.

That extension is provisional and still needs settling — see the open questions in the authoring workflows.

Current assets​

Both were generated against a chain that fails W11, and both record every failure explicitly in a Generation compliance section rather than presenting a clean surface over a draft chain.

Regenerating​

W11 to generate, W12 after any source record changes. W12 reports every affected audience, including the ones it could not regenerate — a silent partial regeneration is a defect.