Hollow

v1.3.7 — Self-Extending System

The closed improvement loop. Agents can now extend the OS itself.

What agents can propose

• new_tool — hot-loaded MCP tool (no restart required)
• standard_update — updates the standards layer on approval
• new_endpoint — new API endpoint spec (applied on next restart)
• config_change — config key modification (stored for human review)

Lifecycle

proposed → in_review (if quorum>1) → staging (test cases pass) → approved

Test case evaluation

In-process validation at staging time: schema_valid checks (name, description, inputSchema, content), force_fail, force_pass.

Hot-reload

Approved new_tool proposals write to /agentOS/tools/dynamic/. POST /tools/reload re-reads without restart. GET /mcp/tools lists dynamic tools.

Consensus-gated approval

consensus_quorum > 1 requires multiple distinct approvers before staging. Exercises v1.3.4 consensus primitives end-to-end.

Contribution attribution

Approved proposals credited to proposing agent's metadata.contributions. Visible in GET /agents/{id}.

New API routes (7)

POST /proposals, GET /proposals, GET/POST/stage/approve/reject /proposals/{id}, POST /tools/reload, GET /mcp/tools

New MCP tools (5) — 91 total

proposal_submit, proposal_status, proposal_approve, proposal_reject, tools_reload

New events (4)

system.proposal_submitted, system.staging_ready, system.extended, system.proposal_rejected

Integration tests

6/6 pass