ADIP Control Plane

This workspace is the governed decision plane for Agnostic Distributed Intent-Driven Projection (ADIP).

It owns the path from admitted semantic authority to a signed, target-bound projection package, then evaluates returned evidence and records lifecycle decisions. It coordinates the existing SEJ runtime resolver and SEJ runtime projector; it does not duplicate their mechanics.

propose
  -> validate and admit
  -> retrieve
  -> resolve
  -> qualify target
  -> plan and project
  -> select bindings
  -> issue target-bound package
  -> receive evidence
  -> evaluate conformance
  -> decide lifecycle

Existing runtime dependencies

• ../sej-runtime-resolver executes approved, domain-neutral SEJ primitives.
• ../sej-runtime-projector plans and safely reconciles declared workspace file bodies.

The control plane owns orchestration and semantic decisions. Neither dependency may silently acquire authority, choose product meaning, or make lifecycle decisions.

Workspace map

• apps/cli is the first human and automation doorway.
• packages/authority-* define, validate, admit, and retain durable authority.
• packages/semantic-* retrieve applicable authority and close it into a resolved graph.
• packages/target-qualification proves whether a target is eligible.
• packages/projection-orchestration coordinates projection without owning projector mechanics.
• packages/binding-registry selects admitted concrete capability bindings.
• packages/evidence-ledger retains immutable receipts and observations.
• packages/conformance evaluates declared obligations against evidence.
• packages/lifecycle-control records promote, revise, supersede, rollback, quarantine, and retire decisions.
• contracts is the language-neutral interchange boundary.
• docs records architecture and decisions.

First vertical slice

The initial slice should use canonical JSON files plus a local searchable index, one local Node target profile, one admitted binding, one real invocation, and one conformance obligation. Breadth comes after the receipt chain closes end to end.

Implementation is incremental. Milestone 1 now provides the authority and receipt contract spine: strict canonical JSON and hashing, scenario validation, a local content-addressed immutable registry, review-bound admission, and an append-only evidence ledger. Retrieval through CLI composition remain later phases.

See IMPLEMENTATION_PLAN.md for phase order, exclusions, persistence and hashing rules, integration ports, fixtures, acceptance criteria, and the complete MVP definition of done.

Scaffold verification

npm test

The verification command checks that the declared modules, action files, contracts, and documentation remain present.