Repository navigation
Feat/interop selfdir - #24
azzizzybud wants to merge 24 commits into
Conversation
…fy maat_judge DEFER flattening
|
Please explain with as much details as you can what you are trying to do here and why? Otherwise I will have to reject this pull request. |
|
Hi Volotat, Thanks for asking — I should have led with this. Here's exactly what the PR is and why. What it does (all additive and reversible): Tool-calling (interop). A literal-ASCII … protocol the model can emit during generation in serve.py, executed against a small registry, with injected back into the stream. No tokenizer change — the markers are ordinary bytes, so vocab stays 265 and every existing checkpoint loads unchanged. The registry ships with (a) a local port of the four Ma'at governance gates, and (b) a generic HTTP/JSON bridge (stdlib urllib) so the model can call an external endpoint — an MCP server or another agent. My goal is a model that can run locally and independently — keep learning, act on tools, and be accountable — without a human watching it. Each piece is one leg of that: act (tool-calling), steer (self-direction), prove (receipts + health cert). It extends the README's own motivation — "a model that is genuinely yours… that keeps learning… nobody else can take it away" — by giving that model agency and an audit trail rather than just a chat window. What I'm explicitly not claiming: The self-directed learning and health cert build the channel and the diagnostic, not a capability result. The model is toy-level; whether it learns to use these well is open. They're structured so they can't hurt the run either way. No tokenizer/vocab change; existing weights load unchanged. |
…t#24 - HANDOFF.md: state for moving the work to a GPU box (same-path clone, env, opencode session, provider endpoint, next inventory). - CHANGELOG.md: v0.1.0-mirror snapshot. - requirements.txt / requirements-corpora.txt; make setup now installs from them (CPU torch still pinned separately). - UPSTREAM.md: pin the synced upstream commit; the sync script now tags each sync upstream-YYYYMMDD, matching what the doc promised. - HARDENING.md: record patch 0008 and a "deliberately not carried" note for PR volotat#24.
…t#24 - HANDOFF.md: state for moving the work to a GPU box (same-path clone, env, opencode session, provider endpoint, next inventory). - CHANGELOG.md: v0.1.0-mirror snapshot. - requirements.txt / requirements-corpora.txt; make setup now installs from them (CPU torch still pinned separately). - UPSTREAM.md: pin the synced upstream commit; the sync script now tags each sync upstream-YYYYMMDD, matching what the doc promised. - HARDENING.md: record patch 0008 and a "deliberately not carried" note for PR volotat#24.
…t#24 - HANDOFF.md: state for moving the work to a GPU box (same-path clone, env, opencode session, provider endpoint, next inventory). - CHANGELOG.md: v0.1.0-mirror snapshot. - requirements.txt / requirements-corpora.txt; make setup now installs from them (CPU torch still pinned separately). - UPSTREAM.md: pin the synced upstream commit; the sync script now tags each sync upstream-YYYYMMDD, matching what the doc promised. - HARDENING.md: record patch 0008 and a "deliberately not carried" note for PR volotat#24.
No description provided.