AGENTIC COURSE-REDESIGN PROJECT - AUTONOMOUS RUNTIME NOT ACTIVE

This project scaffold is ready for a lecturer-guided first run. Its AGENTS.md,
selected platform adapter, specialist definitions, control templates and
skills support the gated manual workflow immediately after Gate 0A and Gate 0 approval.

The top-level state `candidate_not_active` means something narrower: no
autonomous reusable runtime is activated, no standing schedule is registered,
and no recurrence may run. Installing this scaffold is not activation.

Before any course source path, filename, list, read, copy, hash or intake:

1. record and fingerprint Gate 0A material/environment eligibility without
   exposing source details;
2. in a personal/unmanaged environment, proceed only for privately owned or
   rightsholder-authorised material, or appropriately licensed/public material
   with explicit AI-processing authority; public availability alone is not
   enough;
3. route institution-internal/restricted material without source/path leakage,
   and fail closed on mixed/uncertain material until segregated or clarified;
4. for an approved institutional exact environment, record policy reference,
   approved scope and non-expired expiry.

Only after Gate 0A permits processing:

1. keep one course only in this project;
2. place copied current materials in `00_Source_Materials` and contextual
   evidence in `00_Context`;
3. exclude student personal data, submissions, grades, credentials and secrets
   unless a separately authorised institutional workflow explicitly permits
   them;
4. create and verify the exact source manifest;
5. obtain lecturer confirmation of source classes, teacher-only assessment
   boundaries, role/tool/egress permissions and output audiences;
6. compute and review the versioned source-access-policy fingerprint; and
7. record Gate 0 approval with exact matching manifest and policy lineage.

The guided workflow then requires Gate 1, all five preliminary Stage A returns,
HITL 1, deeper research and reconciliation, HITL 2, an approved production
blueprint, independent artefact QA and HITL 3. No old gate approval carries to a
new run, source set, policy version, context version or plan version.

After a successful course run, the lecturer may choose a separate reusable-
system review. After the explicit requested/declined response, the course run
is terminal `complete_dormant`, `active_run_id` is cleared, and the run never
resumes. One informational trigger-guidance offer explains that a manual or
scheduled trigger creates a fresh run and lineage. Any proposed change must remain an inactive, versioned candidate
until its validators and fresh-run simulation pass. A later activation decision
must name the exact validated proposal ID/version and cite the validation,
residual-risk and rollback records.

A standing schedule is a still later decision. It may be registered only for
the exact active runtime and an expiring contract that binds the course/project,
mission, Gate-0A eligibility fingerprint, source-policy version/fingerprint, permitted source classes and output
audiences, assessment-security boundary, protected root, IANA timezone,
recurrence, gate ceilings, retries, stop conditions, unique outputs and
no-immediate-run rule. Registration requires the exact three-line lecturer reply
defined in state.json. Registration never triggers an immediate content run.
