wiki/projects/side-projects-desktop/consent-scoped-communication/ai-readiness
AI Readiness / Machine-Readable Intent
wiki/projects/side-projects-desktop/consent-scoped-communication/ai-readiness/index.mdRendered from markdown source. Open raw source on GitHub.
AI Readiness / Machine-Readable Intent
This page compresses the AI readiness note into the consent-scoped communication branch.
Source Artifact
- Source role:
standard_named_source - Inbound original: ai_readiness_machine_readable_intent_one_pager.md
- Standard-named source: 20260710__CONTINUITAI__BRIEF__MACHINE-READABLE-INTENT__v1__ai-readiness-begins-with-intent.md
Working Read
The note argues that AI readiness starts with machine-readable intent: inventory data surfaces, assign guardianship, and gate human and automated access through explicit purpose-bound policy.
Core Claim
If intent is not machine-readable, AI will treat access as permission. Structural clarity is the first safety step.
Key Ideas
- Machine-readable intent is the missing layer.
- Permissions and cultural norms are not enough.
- Guardianship and purpose statements must be explicit.
- AI capability without constraint becomes liability.
Related Pages
- Consent-Scoped Communication
- Substrate Specification
- Infrastructure Opportunity
- Internal Briefing
- Continuity Office
Attractor Bridge
Notes
- This is a source-anchored readiness note, not a canon claim.
- Keep the machine-readable intent framing central.