Start / Rules we enforce
Reuse Policy
What an agent may do with a source is decided by its authority tier, not by how useful the
text looks. The tier is recorded in manifest/files.csv and routed in
opportunities/routing.csv, both in the artifact store.
| Authority tier | reuse_permitted |
What the agent may do |
|---|---|---|
policy |
true | Quote verbatim. These are our own rules. |
authoritative_submitted |
true | Quote verbatim or paraphrase as our language, subject to review. |
derived_aggregate |
true | Cite as an observation about the corpus, never as a fact about a client. |
issuer_provided |
false | Cite as a compliance requirement to satisfy. Never render as our prose. |
third_party_model |
false | Read for orientation only. Never quote, never paraphrase. |
reference_copy |
false | Read for orientation only, pending authorship confirmation. |
third_party |
false | Read for orientation only. Never quote, never paraphrase. |
bafo |
false | Do not open. Routes to the pricing register behind an explicit acknowledgement. |
unknown |
false | Do not use until a reviewer assigns a tier. |
The failure this prevents
A drafting agent that finds well-written text does not know who wrote it. Issuer instructions read like requirements we wrote. A competitor's proposal reads like ours. Publishing either as Qualus language is a reuse violation that survives review precisely because the prose is good.
Changing a tier
Tiers are data. Edit promotion_decision in manifest/authority_review_queue.csv and
rebuild. Never edit a generated page, and never change the pipeline to promote one file.