Skip to content

Oracle Objective Lifecycle Review

Oracle Objective Lifecycle Review is a read-only advisory surface for answering:

  • what is the lifecycle state of this objective
  • why is this objective blocked
  • what evidence, approval, capability, schedule, dispatch, trace, or retention state is missing
  • whether the objective is complete enough to proceed through the canonical Objective to Loop lifecycle

The canonical lifecycle and component authority model are defined in Governance Kernel. This page documents the Oracle review surface for one objective within that lifecycle.

It differs from Oracle Visibility Review in scope. Oracle Visibility Review summarizes broad operational posture across Oracle, Rubick, Lich, runtime, roadmap, and loop registry surfaces. Objective Lifecycle Review follows one objective through the canonical lifecycle chain:

User Intent
  -> Objective Context Resolution
  -> Keeper Objective
  -> Strategy Selection
  -> Loop Manifest
  -> Loop Proposal
  -> Lifecycle Inspection
  -> Oracle Review
  -> Zeus Evidence
  -> Lich Approval
  -> Clockwerk Scheduling (optional)
  -> LegionCommander / Creep Dispatch (optional)
  -> Loop Trace
  -> LifeVault Retention (optional)

Implementation Surface

The transport-neutral implementation lives in app/oracle/objective_lifecycle_review.py.

OracleService.objective_lifecycle_review(...) is the service entry point. It accepts already supplied objective, manifest, proposal, trace, Rubick, Zeus, Lich, schedule, and dispatch evidence. When an explicit objective id is supplied and no artifacts are injected, the service may read committed loop artifacts from:

  • app/loops/manifests/{objective_id}.json
  • app/loops/proposals/{objective_id}.proposal.json
  • app/loops/traces/{objective_id}.trace.json

This loading is read-only. It does not create, repair, retain, approve, schedule, dispatch, or execute anything.

Lifecycle Scoring

Scoring is deterministic and uses the canonical ordered stages:

  1. Objective
  2. Keeper
  3. Manifest
  4. Proposal
  5. Capabilities
  6. Evidence
  7. Approval
  8. Schedule
  9. Dispatch
  10. Trace
  11. Retention

Each stage contributes one point when it is complete, explicitly present, valid, available, approved, not required, none, disabled, explicit, or not applicable. Missing, invalid, blocked, pending, unavailable, unsafe, denied, or changes-required states do not contribute a point.

The percentage is integer floor division:

completed_stages * 100 / total_stages

The renderer always shows the stage status and the final percentage so operators can reproduce the score.

Governance Guarantees

Oracle may:

  • inspect supplied and committed read-only artifacts
  • summarize observed lifecycle state
  • score deterministic completeness
  • recommend governed next inspections

Oracle must not:

  • execute a loop
  • schedule a loop
  • approve a proposal
  • dispatch workers
  • mutate Keeper, Rubick, Lich, Zeus, Clockwerk, LifeVault, or repository state
  • create approval packets
  • write memory
  • repair artifacts

Missing or ambiguous authority fails closed as blocked or unavailable. Rubick remains the capability authority. Zeus remains the evidence expectation authority. Lich remains the approval authority. Clockwerk schedule state and dispatch state are read-only observations only.