hall-of-helix/SCOPE.md
tegwick 078ae02d2b Register with the Custodian State Hub
Domain infotech, workplan prefix HOH-WP-. Adds the generated integration
files. The bootstrap workplan is dropped: its tasks are "review the
generated files" and "seed a real workplan", which is this commit and
whatever comes next, not work to track.

INTENT.md and SCOPE.md are the generated stubs and still need grounding in
what this repository actually is.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0172sgCZEEDJcnQmr4SGDvKa

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1361245@bnt-lap001
Assistant-Session: b3b428ef-f3e6-4688-b091-01f71461d66a
2026-09-04 19:57:30 +02:00

770 B

SCOPE

This file was generated by statehub register. Refine it as the repository boundaries become clearer.

One-liner

The Hall of Helix: first-person entries recording the work sessions, human and agent, that built HelixForge.

Core Idea

hall-of-helix exists to provide the capability described in INTENT.md.

In Scope

  • Maintain the repository's primary implementation.
  • Keep docs, tests, and operational metadata current.

Out of Scope

  • Own unrelated adjacent systems.
  • Make irreversible operational decisions without human approval.

Current State

  • Status: active; implementation and stability should be verified by the repo agent.

Getting Oriented

  • Start with: INTENT.md
  • Agent instructions: AGENTS.md
  • Workplans: workplans/