Repository navigation
FreeOS self-growth loop works end to end - #4
Merged
Merged
Conversation
Add `freeos org loop run` so a blueprint compiles into chat-usable colleagues, publishes an asset pack, applies it to openXYOS (live HTTP or a durable local mirror), imports the control plane back, and proves host governance blocks high-risk tools. Co-authored-by: XYAI Labs <haoboy8@gmail.com>
Co-authored-by: XYAI Labs <haoboy8@gmail.com>
XYAIStudio
marked this pull request as ready for review
September 15, 2026 03:27
This was referenced Sep 15, 2026
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
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
The FreeOS ↔ openXYOS self-growth loop is now a runnable product path, not a scaffold.
FreeOS produces AI employees, skills, plugins, and MCPs. Those assets apply onto openXYOS-shaped surfaces. Control-plane blueprints, catalog, and policies import back and register real FreeOS chat agents. High-risk tools are blocked on the host tool path.
One command proves it:
Or
bash scripts/org-loop.sh. WithOPENXYOS_BASE_URLset, outbound packs POST/PUT to the live control plane. When the sidecar is down, bundled fixtures +{FREEOS_HOME}/openxyos-mirror/still complete the loop.Target branch
mainType of change
What landed
freeos org loop run— compile demo blueprints →draft→active→ spawn agents → publish pack → apply → import back → prove governanceexecute=falsefreeos org assets apply— real HTTP client for/api/employees,/api/talent,/api/plugins,/api/module-settingsplus a durable local mirrorshadow|activewritesorg-<slug>into the hostagentstable, skill packages, and tenantrouting.jsonOrgGovernanceMiddlewareis first in the harness middleware chain; pending/deny returns an error ToolMessage and does not run the toolresolve_user_agentresolves colleague slugs/names; MEMORY/knowledge sync intoorg-knowledge/live/<slug>/tests/fixtures/org-loop/and packagedsrc/octop/modules/org_os/loop/data/Test plan
CHANGELOG.md/ README /docs/asset-loop.mdupdatedmake all(CI on this PR)Checklist
CHANGELOG.md