REFERENCE · scope stated in document
Implementation templates
162 words. Reference document; its scope and limits are stated inside it. Source: Templates/README.md. Reference modules, shelf 4 of 8; library release 2026.09.12-g40.
The 12 JSON files in this folder are working data contracts and fictional examples, not populated client reports. null means unknown or not yet measured; it must not be converted to zero. A draft or unapproved record is not authorization to publish, delete URLs or alter accounts.
Start with project-intake.example.json, then complete the applicable source-fact, URL, engine-policy and metric records. Use the claim register for evidence, the release acceptance record for actual test output and the maintenance ledger for future changes. Keep Tier 13 retired in the client-scope record.
The example engine policy allows named search bots while denying selected training/product-use tokens. It intentionally leaves unlisted consumers to the wildcard rule and is NOT a comprehensive opt-out from all training. Google-Extended has additional grounding consequences. Review the engine control matrix before generating any policy.
No production key, private user record or live account configuration is included. The robots generator requires an approved policy unless explicitly run in example mode.
Back to the shelf in the room · Reference modules
