Overview
ArcCharter is the per-run identity and authorization layer for ArcFlow. Before any run starts, ArcCharter issues a short-lived signed token that declares exactly which tools the run may call, which secrets it may read, and how long it has to complete. The run's every tool call is checked against the charter — a call outside the declared scope is denied and logged as a security event.
ArcCharter is referenced as capability AF-12 in the ArcFlow capability matrix. It has not yet started.
Core concepts
Charter
A signed JWT issued by ArcCharter at run start. Contains: run ID, flow ID, declared tool set, Vault secret refs allowed, max wall-clock, issuer (ArcCharter service). Signed with the Grid's root signing key.
Scope enforcement
Every tool call in the run presents its charter. The tool layer validates the charter signature and checks that the called tool is in the declared set. Expired charters are rejected regardless of scope.
Vault binding
Secrets are not injected into the run environment. The charter is presented to Vault to fetch each secret at the point of use. Vault checks charter validity and scope before issuing. Secrets never persist in the run environment beyond their use window.
Charter schema
{
"run_id": "run_01J...",
"flow_id": "flow_01J...",
"issued_at": 1728000000,
"expires_at": 1728003600,
"tools": ["http.post", "supabase.select", "vault.get"],
"secrets": ["SENDGRID_API_KEY", "STRIPE_WEBHOOK_SECRET"],
"iss": "archarter.arc-grid.internal",
"sig": "ed25519:..."
}Run lifecycle
- ArcFlow engine submits run intent to ArcCharter with declared scope
- ArcCharter validates the flow definition against allowed scopes for that tenant
- Charter JWT issued and returned to the engine
- Run executes; every tool call validates charter inline
- Charter expires or is explicitly revoked at run end
- Revocation log written to audit trail
ArcFlow integration
ArcCharter is transparent to ArcFlow workflow authors. The engine handles charter issuance and presents it to tools automatically. Authors declare tool scope in the flow YAML; the engine turns that into a charter request.
# arcflow.yaml (author-facing)
charter:
tools: [http.post, supabase.select]
secrets: [SENDGRID_API_KEY]
max_duration: 3600Status
ArcCharter is referenced in the ArcFlow capability matrix (AF-12) but has not started. It will be designed alongside ARCFLOW.3 (runtime hardening). The schema above is a draft — final design pending.