| name | 0.5.2-understand-way_of_life_framework |
| description | ["0.5.2"] |
| the usage discipline for agents distilled from the worked example | KBs first, compile on demand, worklists dra |
understand-way_of_life_framework
CALL NUMBER: law.way_of_life_framework : ee_v2_layer(10), map_layer(5), gauge_dinf_conjecture_unverified(3), lfpoop_lib(3), app_layer_unverified(1)
DEFINITION: the usage discipline for agents distilled from the worked example: KBs first, compile on demand, worklists drained on heartbeats
Invoke this skill to understand way_of_life_framework down to its primitives. The RELATIVE ROOT below is the least-fixed-point closure of everything it bundles from — the full import cone, grouped by the lib each prim comes from. Projected from a prover-typed KB (MAP/SWI-Prolog consistency gate): every reference below resolves.
THE RELATIVE ROOT (the import cone, by lib)
from app_layer_unverified
- chain_protocol (d1): the human-interaction contract: state a desire, release, receive emergence, select branches, revise, re-enter
from ee_v2_layer
- ee_journey (d2): the 72-node emergence-engine walk: dir-is-the-state, per-order horizon, gated emissions
- fixpoint_meter (d3): zero newly-accreted structure across a cycle = stabilized; the kernel's own closure clause, measured
- metacompiler (d3): parses any chain-notation prompt into a kernel and runs it as a gated cycling KB compiler
- curried_compiler (d4): compile(kb, X, op): CEL context from the relative root of X, one seat, accrete, re-check — every agent is this curried
- cycle (d4): one walk of a kernel's nodes by fresh seats, ending in a harvest
- kernel (d4): a parsed recursive chain: named nodes with substeps plus a closure clause
- relative_root (d5): the least-fixed-point closure of everything X bundles from, walked to prims or to consumers, tagged by origin lib
- harvest (d5): the cycle-end dump of emerged concepts and relations into the persistent KB
- chain_notation (d5): the [Name]: N.Node: Na.step format — a prompt whose structure IS the program
- worklist (d6): the prover-minted backlog: define (referenced-but-undefined), connect (orphans), reconcile (near-duplicates)
from gauge_dinf_conjecture_unverified
- order_gradation (d2): the ^4: grade-shifts of the position triple; the grading becomes dynamics the moment a grade-raising operator exists (emission, next_level, retype_up)
- position_triple (d2): the 3 in the 81 law: the three positions of D=[D->D] — object, map-space, evaluation; EE's layer frames are literally these (what-is / how-build / build-this)
- grade_raiser (d3): the operator that makes gradation dynamical: emission at pass end, lfpoop next_level with goldenization, the tower step
from law
- dogfooding_loop (d1): run the system on its own design KB: proving the plan fortifies the plan and mints its backlog
- the_81_law (d1): to generally explain a thing to the point you can program it, apply it to itself 3^4 times — one triple (concept, general constructor, specific instance) at four scales; explanation is complete when it has become a generator
- collapse_principle (d2): every planned integration is first a certified KB region, not code — the long-wise reification is skipped until the law fires
- automatability_test (d2): a process is automatable under a view iff the view's self-application trace reaches fixpoint — metacompile the view, run it, read the meter; non-convergence means re-gauge the view, not give up
- futamura_tower (d2): the projection ladder: specializing an interpreter to a program yields a compiler; specializing the specializer compounds
- order_3_introspection (d2): the automator's requirement: observe the output, observe the observer (the authority split), observe the observing protocol (the meter and rulebook) — an order-3+ cybernetic system applied to itself
- recompilation_law (d3): bind a KB region to code only when its output is needed without lookup — reproduce with specialization
from lfpoop_lib
- lfpoop_ladder (d4): the 10-rung realization ladder of ONE identity: function, program, graph_entity, skill, manual, agent, application, distribution, golden_artifact, compiler_improvement; next_level admits exactly the next rung
- architecture_chain (d5): the 8-link chain: code_thing, graph_mirror_entity, runtime_object, actor, network, compiler, meta_compiler, repository_ecology
- goldenization (d5): hot artifacts cool through execution, testing, witnessing — the cooling dynamics of the ladder
from map_layer
- authority_split (d3): seats author candidate facts only; the engine holds source facts; a seat can never witness itself
- map_prover (d6): SWI-Prolog closed-world checker behind a typed construction boundary; the consistency typer for everything the seats emit
- certificate (d7): a replayable proof envelope over a construction: subject, payload, kappa, sha — monotone, never uncertifies
- consistency_typing (d7): the KB cannot become internally inconsistent: every emission passes the typer or its violations are named
- soup_frontier (d7): the named violations when a construction fails: dangling, orphan, ungrounded — the retry signal and the work queue
CONSUMERS (what needs this)
toy_app
Projected from the the_toy_stack KB (57 concepts / 84 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.
(leaf — this is an actual skill.)
