ADR-0019: Execution Context as a Governed Platform Resource

Status: Proposed — direction only, not implemented Date: 2026-07-27

Context

With enough independent agent execution contexts running against the Bluefly platform (Claude interactive, Claude background jobs, other assistants, Oracle-side agents, NAS-side agents), execution context itself needs to become a governed, first-class concept — same tier as runtimes, repositories, and configuration.

This emerged from a concrete incident: feedback describing a "repository-divergence Doctor" / Cedar policy-drift investigation was pasted into a session that had never done that work — it belonged to a different parallel execution thread. The correct response was refusing to claim that work; this generalizes to "execution-context fragmentation" as a real underlying problem, distinct from any single agent's mistake.

Decision (proposed shape)

Execution Context
    Context ID
    Agent
    Authority
    Credentials
    Filesystem
    Conversation
    Memory
    Capabilities

Every receipt opens with an Execution Context block (which agent, which filesystem, which credentials, what authority) and, where relevant, a separate Operator Context block (interactive terminal, authenticated) — so two receipts about the same host from two different contexts can both be true without contradiction, instead of reading as one "fixing" or "contradicting" the other.

Proposed mandatory preflight for any agent starting work: 1. What system am I running on? 2. What credentials do I possess? 3. What authority do I have? 4. Which runtime is authoritative? 5. Which previous execution context am I continuing from? 6. Can I actually see that context?

If #6 is no: stop claiming continuity.

Status

Not yet implemented anywhere — no Conformance Registry, no receipt schema enforcement, no preflight tooling. The core discipline (narrow claims, continuity preflight before treating a pasted description as this session's own prior work) is already codified as binding practice in standards/core/evidence-reporting-standard.md §10–11. This ADR is the standing direction for making that discipline structural (a first-class resource/schema) rather than only a written-down manual practice.

Consequences

When asked to help design or build this (a Conformance Registry, a receipt schema, a preflight check), treat it as new work grounded in this stated intent — not as something already existing.