Files
steev/docs/LEGACY-INGEST.md
T
2026-06-18 03:03:49 -04:00

3.3 KiB

Steev Legacy Ingest

Schema: cortex.steev.legacy-ingest.v1 Last reviewed: 2026-06-18

This file is Steev child-local operator state. It is not Cortex OS Core SOT, not Runtime authority, not Profile Exposure approval, not send approval, not credential access, not Memory Domain approval, and not product readiness.

Steev legacy work is assessed by intention first. Old work is kept, ported, archived outside the umbrella, deferred, or rejected only after the useful intention is identified and compared against current Steev main.

Rules

  • Do not import raw messages, mail bodies, contacts, calendar details, drive names, endpoint payloads, cookies, credentials, or secret values.
  • Do not install or start Steev, mutate ~/.hermes, broaden Profile Exposure, send messages, write personal surfaces, call providers, or write durable Hindsight memory from this route.
  • Keep legacy records compact: refs, intention, current coverage, decision, closure gate, and forbidden effects.

Current Gates

Steev Identity And Master Reference

  • Source refs: AGENT.md, docs/STEEV-MASTER.md, CONTRACT.md, DISCLOSURE.md, and manifest.yaml.
  • Intention: preserve JP's personal-agent identity, role, mission, boundaries, bilingual posture, delegation rules, and no-autonomous-send policy.
  • Current coverage: met by current profile docs, manifest, disclosure, and validator.
  • Decision: keep as canonical child-local profile reference.
  • Closure gate: any identity change needs Steev route validation and must not alter Core truth, Profile Exposure, Runtime, send authority, or memory access.

Personal-Agent Context Runtime Package

  • Source refs: docs/prd/2026-06-14-personal-agent-context-runtime-prd.md, docs/issues/2026-06-14-personal-agent-context-runtime-work-orders.md, docs/sandcastles/2026-06-14-personal-agent-context-runtime-sandcastle.md, docs/supersession/2026-06-14-personal-agent-context-runtime-supersession-register.md, and docs/contracts/*.json.
  • Intention: standardize personal-agent surfaces for BlueBubbles, Proton/rclone, Secondbrain proposal/apply routing, Conductor/Curator handoff, runtime readiness snapshots, and Desktop exposure without creating duplicate live connectors.
  • Current coverage: met as contracts, redacted refs, supersession register, and validator-backed route-local evidence.
  • Decision: keep as accepted Steev package material; do not import raw personal data or old sandcastle mass.
  • Closure gate: live Runtime, browser host, provider, send, write, Profile Exposure, or durable memory behavior requires explicit governed approval.

Core/Seed Readiness Boundary

  • Source refs: docs/evidence/2026-06-15-personal-agent-core-seed-readiness-reconciliation.md and docs/evidence/2026-06-15-personal-agent-current-governed-boundary.md.
  • Intention: pin what Core/Seed/Proton evidence can inform Steev without letting Steev claim branch authority, product readiness, or runtime readiness.
  • Current coverage: met as redacted reconciliation evidence and governed boundary notes.
  • Decision: keep as reference-only; do not mutate Core, Seed, Proton, Keyvault, OpenDesign, or sibling repos from Steev.
  • Closure gate: future productization or broader readiness must enter Core/Seed through exact source-lock refs, focused validators, and explicit approval.