active development / public preview

Human authority. Structured AI collaboration.
Verifiable decisions.

APCP Conductor coordinates people, independent AI collaborators, and a bounded execution agent — through structured packets, exact-action approval, and a record that doesn't move once it's written.

See who does what Read the actual log

6: canonical packet types
4: status levels
1: human authority

provenance.log

canonical artifacts

Six packet types. One shared record.

Shape identifies what an artifact is. Color identifies its condition. Neither depends on the other alone.

work request

Task

Purpose, scope, constraints, owner, and acceptance criteria.

returned output

Result

What was produced, observed, or learned in response to a Task.

authority record

Decision

A choice, approval, rejection, or disposition with the reasoning kept intact.

evidence check

Validation

Expected state, actual state, evidence, warnings, and outcome.

supporting context

Reference

Canonical material that informs work without duplicating it.

controlled stop

Pause

An explicit hold that preserves state, reason, and restart condition.

four roles, deliberately unequal

Capability and authority are never the same thing here.

Something can be able to act without being allowed to decide. That split is the whole architecture.

human

Sets intent, holds authority

Grants scope, sets cost ceilings, approves anything irreversible. No packet reaches an authority state without this.

conductor

Routes, validates, remembers

Holds the packet lifecycle, the audit trail, and every decision's evidence. The only place state actually lives.

collaborators

Reason independently

Separate AI systems analyze, critique, and propose — without collapsing into one unverifiable answer.

dca

Executes, never decides

Sensory and motor access to a real environment. No standing authority, no memory of its own between actions.

positive authorization

No approval means it doesn't run. Not "probably fine" — doesn't run.

Every approval is bound to the exact action, the exact target, the exact hash. If the action changes after approval, the approval is void. Lost connection, a timeout, ambiguity, a software fault — every one of these resolves to the same place: nothing executes.

PASS WARN FAIL CRITICAL

Exact-action bindingA different action always needs a different approval. Nothing is approved "in general."

Fail closedExpired, unverifiable, or ambiguous authorization is treated as no authorization.

Immutable recordDecisions and their evidence don't get edited after the fact — corrections are new entries, not silent fixes.

Separated authorityBeing able to execute something is never the same fact as being allowed to.

where this actually is

Built in stages, on purpose.

Shipped

Packet protocol & local Conductor

The six packet types, review queue, audit log, validation snapshots, bundle import/export.

In progress

DCA & mobile approval

The execution interface, observation channel, and a thin approval client for the one thing that still needs a human's actual attention.

Distributed collaboration

Secure remote execution, cross-model handoffs reviewed the same way local ones are, real deployment discipline.

apcp conductor

Under active development. The log is the pitch.

There's no polished demo yet — there's a working protocol, a real audit trail, and a lot of decisions that were argued out, not assumed. If that's the kind of thing you want to watch or contribute to, say so.

Human authority. Structured AI collaboration.Verifiable decisions.