Position IntentDriven within the Agent Development Lifecycle

[dmltdev]

Cloudflare's Agent Development Lifecycle overlaps with IntentDriven, but the two systems operate at different layers.

Direction

Position IntentDriven as the intent, decision, evidence, and semantic-drift layer for an ADLC software factory. Keep IntentDriven platform-neutral and usable for ordinary repository delivery.

Explore

• Add an optional operational route for release, observation, maintenance, and retirement.
• Extend traceability from pre-release evidence into deployments and production signals.
• Model release permissions, escalation, rollout, rollback, and operational drift.
• Capture learning receipts when autonomy stops or fails.
• Preserve the existing small-work, collaborative, and full IDD routes.

Non-goals

• Do not rename IntentDriven to ADLC.
• Do not require Cloudflare or another specific platform.
• Do not force factory-scale ceremony or independently deployable units onto ordinary small work.
• Do not let production behavior silently redefine accepted intent.

Reference

Detailed positioning and open questions: https://github.com/dmltdev/intentdriven/blob/docs/adlc-positioning/docs/ideas/adlc-positioning.md