feat(context): estate orientation package + estate-orient skill#23
Merged
Conversation
todie
force-pushed
the
feat/estate-context
branch
from
July 16, 2026 20:03
3fd9917 to
6a6cb03
Compare
Single-source estate brief rendered into per-harness user context:
- packages/context/{estate,invariants,omp-prelude}.md + render.sh (budget-gated)
- renders ~/.omp/agent/AGENTS.md (shadows Claude-specific CLAUDE.md at omp
user scope), ~/.omp/agent/RULES.md (sticky invariants), ~/.agents/estate.md
(imported by ~/.claude/CLAUDE.md)
- packages/skills/estate-orient: live cluster/GitOps/OpenBao/engram intake
probe shared by all harnesses
Verified live: omp -p answers estate questions from the rendered files and
lists the skill.
todie
force-pushed
the
feat/estate-context
branch
from
July 16, 2026 20:07
6a6cb03 to
47f5124
Compare
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.
What
New
packages/context/— single-source estate brief (clusters, repo map, SOP index, memory-of-record, secrets model, intake protocol) rendered into per-harness user context files, plus a sharedestate-orientskill for live intake.omp-prelude.md+estate.md~/.omp/agent/AGENTS.md~/.claude/CLAUDE.mdomp was inheritinginvariants.md~/.omp/agent/RULES.mdestate.md~/.agents/estate.md~/.claude/CLAUDE.mdvia@~/.agents/estate.mdrender.shis idempotent, shellcheck-clean, and gatesestate.mdat ~2400 est. tokens (currently ~1169).Why
omp had no native user context, so every omp session was oriented by
~/.claude/CLAUDE.md— RTK proxy, Claude hook paths, Claude tool priorities — wrong harness, wasted tokens in GLM/Nemotron lanes. The estate (2 clusters, ~60 ArgoCD apps, litany of SOPs) had no harness-neutral orientation surface at all.Verified
Live
omp -prun after render: correctly answered Lyra/Calico (AGENTS.md), the ApplicationSet apply doctrine (sticky RULES.md), and confirmedestate-orientin its skill list.Post-merge
Run
packages/skills/install.sh(replaces the temporary local copies ofestate-orientwith symlinks) andpackages/context/render.shfrom the main checkout.Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.