Imported from foolishimp/odd_manager (AGENTS.md). Install upstream with npx skills add foolishimp/odd_manager. Copyright stays with the author.

odd_manager Workspace Surface

This workspace is the odd_manager source project. It is an observer and operator-facing control plane for odd_ derived products built on GTL/ABG. It is not governed by a workspace-local odd_sdlc runtime install.

1. Workspace Identity

workspace: odd_manager
project slug: odd_manager
platform: react_vite
active local domain runtime contract: none
project bootstrap: workspace://.ai-workspace/context/project_bootstrap.md
primary authority: workspace://specification/
realization carrier: workspace://build_tenants/react_vite/

2. Agent Operating Rule

start from odd_manager specification, requirements, and ratified design
treat .genesis/odd_sdlc/ and .ai-workspace/runtime/odd_sdlc-* as removed legacy surfaces if they appear in old commentary or generated history
observe odd_sdlc and other odd_ products through their published GTL/ABG ledgers, catalogs, projections, and compatible domain packs
do not install a product-specific builder runtime into this source project to define manager identity
keep ABG runtime truth separate from domain-specific overlays

3. Read First

workspace://README.md
workspace://specification/INTENT.md
workspace://specification/PRODUCT.md
workspace://specification/GOALS.md
workspace://specification/requirements/
workspace://specification/domain/DOMAIN_MODEL.md
workspace://build_tenants/common/design/
workspace://build_tenants/react_vite/
workspace://.genesis/docs/LLM_GTL_APP_BUILDER_GUIDE.md

4. Interpretation Rule

GTL/ABG substrate truth explains runtime mechanics
odd_manager product truth explains the control-plane boundary
observed product packages explain their own domain overlays
copied template/bootstrap history is provenance, not live authority
repository and sibling-workspace context may explain provenance, but must not be used as project identity evidence

GTL Bootloader: Axiomatic Constraint Surface

Version: 3.1.0 Status: Compressed install-time bootstrap Role: Minimal ontology and operating constraints for GTL 3 / ABG 3 work

This is the precreated bootstrap the installer injects into AGENTS.md and CLAUDE.md. It is intentionally compressed. It is authored and validated here; it is not generated by ABG.

Use this document to initialize the LLM with the live axiomatic surface. Use the references at the end to load more detail from the installed runtime or, when present, the source workspace.

Precedence:

source truth is intent -> requirements -> design -> code
this bootstrap is a constrained read model over that truth
if stale code comments or non-constitutional notes disagree, the live constitutional/design surface wins

1. Core Position

GTL is the language. ABG is the canonical interpreter/runtime for GTL.

GTL is:

graph-first
composition-first
recursion-capable
higher-order
engine-agnostic

ABG is:

event-sourced
provenance-carrying
replayable
tail-loop recursive over explicit continuation and child-frontier state

The published module stays stable. Recursive selection opens invocation-local frames; it does not rewrite global module topology.

2. Structural Axioms

Graph is the one first-class structural type.
Node is the typed local locus of graph meaning.
GraphVector is the internal admissible transition contract between nodes.
Context is an externally located, snapshot-bound constraint dimension.
Operator is the effectful action surface.
Evaluator is the convergence and attestation surface.
GraphFunction is the reusable workflow program abstraction.
RefinementBoundary is the explicit lawful refinement or synthesis boundary.
CandidateFamily is the explicit lawful structural-alternative family.
Module is the publication boundary.
Job is the durable semantic work contract over published graph functions.
Role is the semantic capability class.

ABG runtime types such as Traversal, ConvergenceResult, Worker, Run, SelectionDecision, RecursiveContinuation, ChildFrontier, and RecursiveMachineControl are interpreter/runtime artifacts, not rival GTL language ontology.

3. GTL Type Surface

Type	Module	Meaning
`Graph`	`gtl.graph`	Named topology of nodes and graph vectors
`Node`	`gtl.graph`	Typed locus with declared conditions
`GraphVector`	`gtl.graph`	Admissible transition contract between nodes
`Context`	`gtl.graph`	Snapshot-bound external constraint
`Operator`	`gtl.operator_model`	Named capability with regime and binding
`Evaluator`	`gtl.operator_model`	Convergence and attestation declaration
`Rule`	`gtl.operator_model`	Declarative constraint with kind and config
`GraphFunction`	`gtl.function_model`	Reusable workflow template or program
`RefinementBoundary`	`gtl.function_model`	Published lawful refinement boundary
`CandidateFamily`	`gtl.function_model`	Published lawful alternatives over one outer contract
`ContractRef`	`gtl.work_model`	Reference from a semantic job to a published graph-function contract
`Role`	`gtl.work_model`	Semantic capability class
`Job`	`gtl.work_model`	Durable semantic work contract
`Module`	`gtl.module_model`	Publication boundary for GTL artifacts

Public GTL algebra (gtl.algebra):

edge
compose
substitute
recurse
fan_out
fan_in
gate
promote
identity
deferred_refinement
candidate_family
same_object

4. GTL / ABG Boundary

GTL declares:

graph structure
graph algebra
higher-order graph functions
refinement boundaries
candidate families
jobs
roles
module publication
recursion law: declared termination plus declared fold-back contract
semantic jobs over published graph functions, with graph vectors retained as internal realized traversal structure

ABG realizes:

traversal
lawful selection application
materialization
events
projection
provenance
convergence
lineage
role binding
correction/reset
transport
self-hosting consistency checks
recursive machine control

GTL must not depend on ABG runtime modules. ABG may interpret GTL declarations.

5. Evaluator Regimes

Regime	Meaning	Role
`F_D`	Deterministic	Objective checks, schema/tests/hash/provenance checks
`F_P`	Probabilistic	Agent disambiguation and bounded construction
`F_H`	Human	Human approval, rejection, or escalation

Rules:

Deterministic truth closes first wherever possible.
Agent output is not constitutional truth by itself.
Human approval does not override deterministic failure.
Evaluators attest contract satisfaction; operators perform work.

6. Recursive Runtime Contract

Operational GTL recursion in ABG means:

selection chooses only from published lawful alternatives
a recursive choice opens an invocation frame
frame-local publication is fail-closed
recursion progresses as tail-loop control over explicit continuation and child frontier
child completion produces fold-back input, not automatic parent certification
parent truth is re-evaluated after rebind
reset/reopen mints a fresh attempt identity
checkpoints are resumability aids, not a second truth surface

Containment is strict. If frame-local recursion bleeds into global publication or hidden fallback traversal, recursion is broken.

7. Runtime Truth Rules

The event stream is append-only.
emit() is the only lawful write path into runtime truth.
Projection is replay-derived.
Delta is derived truth, not stored authority.
Correction shadows stale truth; it does not erase history.
Transport/prompt formatting is replaceable; manifest/work truth is authoritative.
Derived artifacts are read models and must not outrank constitutional or design truth.

8. Read Next

Methodology master:

public source-of-truth repository: https://github.com/foolishimp/specification_methodology
installed workspace mirror: workspace://.genesis/docs/standards/

Installed runtime details, always present after install:

workspace://.genesis/docs/LLM_GTL_APP_BUILDER_GUIDE.md
workspace://.genesis/docs/GTL_Technical_Guide.md
workspace://.genesis/docs/USER_GUIDE.md
workspace://.genesis/docs/GTL_BOOTLOADER.md
workspace://.genesis/docs/standards/SPEC_METHOD.md
workspace://.genesis/docs/standards/POSTING_GUIDE.md
workspace://.genesis/docs/standards/WRITING_GUIDE.md
workspace://.genesis/gtl/__init__.py
workspace://.genesis/gtl/graph.py
workspace://.genesis/gtl/function_model.py
workspace://.genesis/gtl/algebra.py
workspace://.genesis/genesis/interpret.py
workspace://.genesis/genesis/frames.py
workspace://.genesis/genesis/selection.py
workspace://.genesis/genesis/events.py
workspace://.genesis/genesis/materialization.py
workspace://.genesis/genesis/selfhosting.py

Project-owned surfaces, when present after scaffold:

workspace://README.md
workspace://.ai-workspace/comments/README.md
workspace://.genesis/docs/standards/SPEC_METHOD.md
workspace://specification/INTENT.md
workspace://specification/PRODUCT.md
workspace://specification/GOALS.md
workspace://specification/requirements/
workspace://build_tenants/TENANT_REGISTRY.md
workspace://build_tenants/common/design/README.md

9. LLM Operating Rule

When acting under this bootstrap:

start from live requirements/design, not stale precedent
preserve the GTL / ABG boundary
use the smallest lawful concept that satisfies the requirement
prefer present-tense active truth over migration narration
treat missing traceability as a defect
if a live requirement is not realized, state the gap explicitly
do not invent hidden selection strategy, hidden traversal targets, or rival ontology
if writing under workspace://.ai-workspace/comments/, follow workspace://.genesis/docs/standards/POSTING_GUIDE.md and treat the result as commentary, not law

odd_manager

About