ESTATE_SPEC §1: add project to frozen valid-kinds list#40
Open
kody-w wants to merge 1 commit into
Open
Conversation
The `project` kind is in active use across operator devices today — every project-anchored twin minted by the project-twin neighborhood layer ships with `kind: "project"` in its rappid.json. Existing examples in the wild include the AIBAST twin and every twin hatched by the canonical @kody-w/RAPP-Network/project_twin_agent.py drop-in (see https://github.com/kody-w/RAPP-Network). This PR brings the spec to match that reality: adds `project` to the frozen kinds list and bumps the "frozen as of" date to 2026-05-22. The kody-w/RAPP-Network cross_validate.py script currently emits a WARN for this exact drift; merging this PR clears the warning and makes the two sources-of-truth (this repo + RAPP-Network) align. Rationale for adding rather than retrofitting to `workspace`: - `workspace` already implies a different scope (per the kind list's existing usage — a generic per-user workspace, not project-anchored). - `project` carries clear semantics: "a brainstem twin anchored to and scoped against one project's directory tree." - Twin-aware tools (the canonical Twin agent, twin_egg_hatcher's list_twins, ProjectTwin.list) already special-case kind="project" for discovery filtering. No code changes required — this is a spec amendment to legitimize existing canonical reality. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Adds
projectto the frozen valid-kinds list inpages/docs/ESTATE_SPEC.md§1.Why
The
projectkind is in active use today across operator devices — every project-anchored twin minted by the project-twin neighborhood layer ships withkind: "project"in itsrappid.json. The AIBAST twin uses it; every twin hatched by kody-w/RAPP-Network/project_twin_agent.py uses it.The current spec lists:
twin, neighborhood, ant-farm, braintrust, workspace, hatched, rapplication, prototype, operator.projectis missing.kody-w/RAPP-Network/scripts/cross_validate.pyis purpose-built to surface drift between RAPP-Network's spec and the upstream ESTATE_SPEC frozen-kinds list. It currently emits a WARN for exactly this drift:Merging this PR clears the warning and makes the two sources-of-truth align.
Change
One line in
pages/docs/ESTATE_SPEC.md. Addsprojectto the kinds list; bumpsfrozen as offrom2026-05-09to2026-05-22.Why
project(not retrofit toworkspace)workspacealready has different semantics in existing usage.projectcarries clear semantics: a brainstem twin anchored to and scoped against one project's directory tree.twin_egg_hatcher.list_twins,ProjectTwin.list) already special-casekind="project"for discovery filtering.Test plan
scripts/cross_validate.pyinkody-w/RAPP-Networkshould now pass with no WARN onkind.