Skip to content

QUESTBOOK.md

Latest commit

 

History

History
60 lines (45 loc) · 2.4 KB

QUESTBOOK.md

File metadata and controls

60 lines (45 loc) · 2.4 KB

QUESTBOOK.md — abyss-stack

This file is the public tracked surface for deferred infrastructure obligations that belong to abyss-stack.

Use it for:

  • host-profile rollout and adaptation work that survives the current diff
  • render-truth, doctor, first-run, and runtime guardrail follow-through
  • platform and machine-fit follow-ups
  • high-risk infra obligations that must stay reviewable and human-gated

Do not use it for:

  • source-owned meaning from AoA layer repos
  • silent infra mutation plans
  • secrets, host-local paths, or unsafe operator detail
  • turning every local config experiment into a tracked quest

Frontier / human-gated

  • none right now

Frontier / codex-led

  • ABYSS-STACK-Q-0002 — track host-profile rollout and adaptation obligations without absorbing source-owned layer meaning
  • ABYSS-STACK-Q-0005 — land the first runtime and frontend service contracts for the AoA RPG layer without absorbing upstream meaning
  • ABYSS-STACK-Q-0006 — materialize filesystem-first RPG runtime collections and derived bundles without widening route or quest authority
  • ABYSS-STACK-Q-0007 — unify the runtime diagnostic spine with session-level diagnosis and repair handoff without widening repair authority
  • ABYSS-STACK-Q-0008 — land a route-first ToS graph curation surface without turning Neo4j into source truth

Near

  • ABYSS-STACK-Q-0004 — capture Windows bridge, reference-platform, and machine-fit follow-ups as explicit quests instead of doc drift

Harvest candidates

  • none yet

Quest-harvest posture

aoa-quest-harvest may be installed at .agents/skills/aoa-quest-harvest as a post-session aid for bounded infra follow-through.

  • use it only after a reviewed run, closure, or pause
  • do not use it inside an active route
  • it does not define orchestrator identity
  • it does not replace playbook, memo, eval, or source-owned doctrine
  • do not promote on one anecdotal repeat

Allowed verdicts:

  • keep/open quest
  • promote to skill
  • promote to playbook
  • promote to orchestrator surface
  • promote to proof surface
  • promote to memo surface

Backing files

  • quests/*.yaml
  • schemas/quest.schema.json
  • schemas/quest_dispatch.schema.json
  • examples/quest_catalog.min.example.json
  • examples/quest_dispatch.min.example.json

The files under examples/*.example.json are reviewable examples. They are not generated state, deployed runtime state, or runtime authority.