docs(harness): introduce lifecycle control plane foundation#31
Merged
Conversation
Document Mnemon's lifecycle control plane as a memory-driven orchestration model built around desired state, reconcile, host adapters, projections, and status. The page explains how current memory, skill, and eval loops enter that control path without making Mnemon a host agent runtime. Link the rendered site from the private docs index and both harness documentation indexes, fix the docs home navigation links, and connect the memory-loop and skill-loop pages and design docs back to the same lifecycle control path. Validation: parsed the updated HTML pages with Python's html.parser and checked embedded scripts with node --check.
Capture the YC self-improving company framing as a harness design reference in both English and Chinese. The note translates the article into Mnemon concepts such as canonical context, lifecycle loops, host capability surfaces, quality gates, and human review boundaries. Link the new philosophy note from the English and Chinese harness README entries. Validation: checked markdown links and staged diff whitespace.
Rewrite the lifecycle control plane material around a lighter three-layer model: State/Intent/Reality/Reconcile as the core loop, entity profiles as lightweight classifications, and execution surfaces for projection and observation. Add English and Chinese markdown design notes that mirror the site model and link them from the harness README entries. The model keeps LoopModule, LoopBinding, HostCapability, Projection, Observation, and governance records in a consistent profile framework while positioning Codex appserver as a dynamic observation surface. Validation: checked HTML parsing, script syntax, markdown links, and staged diff whitespace.
Reframe the memory-loop and skill-loop docs around the shared State, Intent, Projection, Reality, and Reconcile model. The site pages keep their existing runtime phase flows while making each loop's lifecycle role clearer. Validation: git diff --check and embedded site script parsing for memory-loop and skill-loop.
Restructure the experimental harness around the lifecycle control model: loops, hosts, bindings, control contracts, and ops. This replaces module/setup naming with loop/ops naming, moves loop manifests to loop.json, and updates host projectors, validation, and Codex app-server eval wiring to use the new layout. The change is intentionally breaking because the harness layer is not yet a stable release-path API. Validation covered harness manifest checks, script syntax, site script parsing, temporary Codex and Claude Code installs, markdown link checks, and go test ./....
Add an interactive harness control browser that explains the current lifecycle layout through source, host projection, and runtime state trees. The page can inspect loops, hosts, bindings, and ops for the selected binding, with bilingual labels and optional repo JSON refresh for live-ish updates. Validation: node parsed the embedded page script and git diff --check passed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR establishes a lifecycle control plane foundation for the memory-driven modular agent harness architecture discussed in #14.
It unifies the current harness vocabulary and repository layout around loops, hosts, bindings, ops, projection, runtime state, and reconcile. It also adds design docs and an interactive harness control UI that shows the relationship between source definitions, host projections, and generated runtime state.
Scope
This is a concept unification and foundation PR. It intentionally does not claim that every loop or host projection is complete or stable.
Included here:
loops,hosts,bindings, andopsFollow-up PRs should tighten individual loop implementations, starting with Codex memory projection semantics and hook/lifecycle guidance alignment.
Validation
make harness-validatego test ./...Refs #14