Expand description
Pack-registered Actions and Functions — the actions!/functions!/
guidance! pack! sections and their registrations (PX2).
Structs§
- Action
Context - What a pack action body receives. The ceiling is the framework’s
enforcement point: every visibility the body produces is clamped (and
the commit path rejects rows that would exceed it), so a pack author
cannot stamp wider than the declared
min_visibilityno matter what the body does (P3: a compile-time AND framework-enforced property). - Action
Edge - One edge a pack action body produces.
kindis the kind display name (the stable identity surface shared with wire formats and rule sources); the framework resolves it through the effective ontology and rejects unknown or computed-only kinds. - Action
Memory - One memory a pack action body produces.
memory_typeis the PACK-LOCAL u8 id (MemoryType::X.id()in the pack crate); the framework remaps it to the effective-ontology id through the pack’s slot at commit. - Action
Product - What a pack action body returns: the memories and edges to commit. The framework validates, provenance-stamps, audits, and commits them — the body cannot bypass any of it.
- Guidance
Entry - One structured agent-guidance entry declared in a
guidance!section (§4.2). Keys and link names resolve against the declaring pack’s own type/kind tables atpack_def()build time — an entry naming an unknown type or kind fails pack load, exactly astype_triples!does. - Guidance
Link - One declared guidance link.
- Pack
Action Def - Signature-level action descriptor carried in
PackDef(and therefore the compatibility fingerprint). Bodies are deliberately absent. - Pack
Action Registration - Compile-time registration emitted by the
actions!section (§4.3: macro-generatedinventory::submit!, one registry — R-P1/R-P2 hold because the operation registry merges these intoentries()). - Pack
Function Def - Signature-level function descriptor carried in
PackDef. Budgets ride the build fingerprint (operational policy, not stored meaning) but not the compatibility summary’s verb identity. - Pack
Function Registration - Compile-time registration emitted by the
functions!section. The body is verbatim source for the declared engine; v1 executesschemebodies through the reasoning crate’s embedded Steel interpreter (pure functions over their typed input — the graph-fed contract is recorded as the boundary in the master plan).datalogbodies are a pack-compile error: Crepe compiles at build time only, and an unexecutable registration would be a phantom surface.
Enums§
- Action
Target - Where an action-produced edge points: a draft key within this action’s product, or an existing memory id.
Functions§
- registered_
pack_ actions - Every registered pack action, sorted by
(pack, verb)— the deterministic enumeration the operation registry merges. - registered_
pack_ functions - Every registered pack function, sorted by
(pack, verb).