docs: clarify deferred mailbox lifecycle
713ef30
docs: explain proactive message recovery
a0adabe
docs: qualify honesty and security guarantees
2ed59d5
docs: make positioning and security coverage explicit
adcc074
docs: explain who should use Philont
5128c19
docs: make the wiki a credible developer entry point
62cdb28
docs: the two mechanisms that guarantee a reasoning tree can produce a signal
Companion to the checkable-object tooth. Documents the refutation pairing (a for-all goal is seeded with
one node a machine can decide, exploiting the asymmetry that confirming needs an argument while refuting
needs one witness) and the per-node acceptance criterion (schema v38), including why the latter counts the
absence rather than rejecting it — a construction node is legitimately task-shaped, a deliberate session's
nodes are questions, and some subgoals are settled only by argument.
d5d97e0
docs: the verification tooth that is not mode-scoped
Deep-Reasoning presented the teeth as formal-mode furniture, which is exactly the hole the Jacobian
session fell into: mode is picked once at entry, so a formal object arriving inside a deliberate session
met nothing. Documents the tooth now standing there, and the three properties that let it default on —
refuse-once, stand down as soon as the session computes anything, and never tell the model what to
conclude ("if the object turns out to be wrong, that is the finding").
934180d
docs: id-provenance guard is on by default (dde7a0a), and scoped to the plan loop
Documented as opt-in in the previous commit, which was the state at 6ab5802; it was
flipped on a day later and its blast radius is the plan loop's own tool runner, so a
scheduled or legacy turn never passes through it. Both the Configuration table and
Plan-Protocol section 7 said otherwise.
36346d9
docs: new Compass page + resync Plan-Protocol, Autonomy and Configuration with the code
The wiki was last synced on 2026-07-11 and described two things that are no longer
true: a compiled service contract as the mechanism that keeps a weak model honest
about an API, and a skill ladder promoted "by successful reuse".
Compass (new page). philont's answer to soul.md, and the authorship runs the other
way: not a persona handed to the agent, but the owner's declaration of where their
second mind should point. Documented by what it mechanically does — the [min,max]
clamp on live trait tuning, focus areas seeded as pursuit rows (prompt injection
alone never reaches the background drivers, which run without the main system
prompt), and the prose injected verbatim — including the design choices worth
knowing: lenient parsing so a hand-written file cannot break startup, and no
backdating so declaring five focus areas does not fire five sessions at once.
Honest scope: no hot reload, no learned focus proposals, and it grants no
permission of its own.
Plan-Protocol §7 — the mechanism loop. The page only covered the protocol the model
walks; the state machine that owns a guide-driven turn was undocumented. The section
explains why two weak models reviewing each other is not automatically worth more
than one model trying twice — the first version wasn't, and production oscillated —
and what the mechanism had to remember for it to become a ratchet. Also records why
the compiled spec was switched off: a wrong call gets corrected by the service, a
wrong contract has nothing to correct it, because the contract IS the corrector.
Autonomy — verify-then-condense. The audit that found none of the three learning
sub-loops closing, the paradigm root cause (online per-artifact attribution), the
judge's grounding-tool rule and its shadow gate, Phases 0 and 3a, and the three
independent defects that were each alone enough to cancel the loop — plus the
general lesson that a learning loop is a product of AND-gates, where the symptom of
a silent veto is not an error but nothing happening.
Supporting: Memory-System corrects what "confirmed" used to mean; Configuration
documents AUX_LLM_* (and that leaving it unset removes the plan reviewer),
compass, AGENT_LANGUAGE and the new flags, and drops the stale claim that
VISION_LLM_* is unwired; Why-a-Cheap-Model gains the failure mode the review
ratchet catches; Selfhood-Engineering §3b, Home and _Sidebar link the new page.
62e4b91
docs: document skill self-repair (H3) + generated capability self-knowledge
The wiki described the self-learning loop as ending at 'deprecated' — the pre-H3
demote-and-forget state. Adds:
- Autonomy-and-Self-Learning: a new 'Skill self-repair' section (EN+ZH) — the
demote_revise trigger, diagnose-from-ledger, reviseRecipe + revision_history,
3-strike retirement, the bounded-repair prompt (no OS-assuming/system-mutating
fixes; inconclusive → no rewrite), default-on flag. Explicitly scoped as
mechanism, not proven efficacy.
- Memory-System: skills are versioned via revision_history, not destructively
replaced.
- Selfhood-Engineering: the learning loop repairs a broken recipe (un-learns a
mistake), and self-knowledge of current capabilities is generated from live
runtime state, not hand-authored.
e12bdaa
docs: sync Home with README's self-learning/evolution facet
459fc0b
docs: align Home with README's Selfhood Engineering repositioning
bf2cfe1
Align with README restructure: plan-gate compute exemption (EN+ZH) + three-tier routing section
cc9207e
Reframe Loop Engineering page as Selfhood Engineering (自我工程)
Rename the wiki's headline concept to Selfhood Engineering: built on
loop engineering + harness design, plus the being-claims (persistent
identity, self-model that can't fake success, intrinsic drives,
continuous memory, deep reasoning). Keep the loop spine intact as the
mechanism evidence. Update Home and Sidebar links; Chinese term is
自我工程.
a9a2f0e
Add Loop Engineering page (bilingual) + link from sidebar/home
Names the loop-engineering discipline and maps Philont's spine onto it (execution-ledger anchor + contract,
goal-loop runtime + trajectory scoring, drives→goal-loops, intent router + force-run guarantee, verified
callable recipes, parallel sub-agents), with file references — mirroring the README's new lead section.
0c4c2b5
Add bilingual developer wiki (12 topics + Home + nav)
31102bf