96  Architecture, Abstraction, and Design

97 Architecture, Abstraction, and Design

Range: 0001-0112.

97.1 Completion

Status	Count
authored	112

Use the summary table for scanning. Each row links to the detailed anchored entry below.

Sigil	Term	Completion	Semantic	Summary
0001	abstraction	authored	reviewed	A deliberate forgetting of detail so larger structure can be reasoned about without drowning in mechanism. Shadow: hiding the only failure that matters.
0002	adapter	authored	reviewed	A negotiated translator between unlike shapes. Use it when two systems must meet without infecting one another. Shadow: adapter jungles that preserve confusion rather than resolve it.
0003	agent {Arch}	authored	reviewed	agent (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies agent, and the review check that would catch drift.
0004	aggregate {Arch}	authored	reviewed	aggregate (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies aggregate, and the review check that would catch drift.
0005	anti-corruption layer	authored	reviewed	A protective seam that keeps one model from polluting another.
0006	API gateway	authored	reviewed	A threshold that centralizes entry, policy, and routing at the edge of a service world. Shadow: a convenience chokepoint that quietly becomes a monolith.
0007	architecture	authored	reviewed	architecture names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies architecture, and the review check that would catch drift.
0008	artifact boundary	authored	reviewed	artifact boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies artifact boundary, and the review check that would catch drift.
0009	assembler	authored	reviewed	assembler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies assembler, and the review check that would catch drift.
0010	backbone	authored	reviewed	backbone names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies backbone, and the review check that would catch drift.
0011	backend	authored	reviewed	backend names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies backend, and the review check that would catch drift.
0012	boundary	authored	reviewed	The line that says where one responsibility ends and another begins. Shadow: porous edges that smear blame, ownership, and test scope.
0013	bounded context	authored	reviewed	A protection against semantic bleed: the same word may not mean the same thing in every subsystem. Shadow: false unification through shared names.
0014	bridge	authored	reviewed	bridge names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies bridge, and the review check that would catch drift.
0015	broker {Arch}	authored	reviewed	broker (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies broker, and the review check that would catch drift.
0016	builder	authored	reviewed	builder names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies builder, and the review check that would catch drift.
0017	bus {Arch}	authored	reviewed	bus (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies bus, and the review check that would catch drift.
0018	capability {Arch}	authored	reviewed	capability (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies capability, and the review check that would catch drift.
0019	channel	authored	reviewed	channel names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies channel, and the review check that would catch drift.
0020	client {Arch}	authored	reviewed	client (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies client, and the review check that would catch drift.
0021	cluster {Arch}	authored	reviewed	cluster (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies cluster, and the review check that would catch drift.
0022	command bus	authored	reviewed	command bus names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies command bus, and the review check that would catch drift.
0023	component {Arch}	authored	reviewed	A bounded unit of responsibility inside a larger design.
0024	composition	authored	reviewed	composition names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies composition, and the review check that would catch drift.
0025	connector	authored	reviewed	connector names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies connector, and the review check that would catch drift.
0026	container {Arch}	authored	reviewed	container (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies container, and the review check that would catch drift.
0027	control plane {Arch}	authored	reviewed	control plane (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies control plane, and the review check that would catch drift.
0028	coordinator	authored	reviewed	coordinator names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies coordinator, and the review check that would catch drift.
0029	core {Arch}	authored	reviewed	core (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies core, and the review check that would catch drift.
0030	coupling	authored	reviewed	The hidden tax paid when change in one place forces change elsewhere. Name it early if you want modularity to survive contact with reality.
0031	daemon {Arch}	authored	reviewed	daemon (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies daemon, and the review check that would catch drift.
0032	data plane {Arch}	authored	reviewed	data plane (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies data plane, and the review check that would catch drift.
0033	decorator {Arch}	authored	reviewed	decorator (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies decorator, and the review check that would catch drift.
0034	dependency inversion	authored	reviewed	Stable policy should not kneel before unstable detail. Shadow: concrete dependencies hard-wired into places that should remain portable.
0035	dispatcher	authored	reviewed	dispatcher names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies dispatcher, and the review check that would catch drift.
0036	domain model	authored	reviewed	The conceptual map of the business world the software is trying to serve.
0037	edge service	authored	reviewed	edge service names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies edge service, and the review check that would catch drift.
0038	engine	authored	reviewed	engine names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies engine, and the review check that would catch drift.
0039	entrypoint	authored	reviewed	entrypoint names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies entrypoint, and the review check that would catch drift.
0040	event bus	authored	reviewed	event bus names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies event bus, and the review check that would catch drift.
0041	event handler	authored	reviewed	event handler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies event handler, and the review check that would catch drift.
0042	executor	authored	reviewed	executor names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies executor, and the review check that would catch drift.
0043	facade	authored	reviewed	A simplified front door hiding a messier interior.
0044	factory	authored	reviewed	factory names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies factory, and the review check that would catch drift.
0045	feature module	authored	reviewed	feature module names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies feature module, and the review check that would catch drift.
0046	frontend	authored	reviewed	frontend names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies frontend, and the review check that would catch drift.
0047	gateway {Arch}	authored	reviewed	gateway (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies gateway, and the review check that would catch drift.
0048	graph	authored	reviewed	graph names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies graph, and the review check that would catch drift.
0049	handler	authored	reviewed	handler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies handler, and the review check that would catch drift.
0050	hierarchy {Arch}	authored	reviewed	hierarchy (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies hierarchy, and the review check that would catch drift.
0051	hook	authored	reviewed	hook names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies hook, and the review check that would catch drift.
0052	host	authored	reviewed	host names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies host, and the review check that would catch drift.
0053	hub	authored	reviewed	hub names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies hub, and the review check that would catch drift.
0054	implementation {Arch}	authored	reviewed	implementation (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies implementation, and the review check that would catch drift.
0055	interface {Arch}	authored	reviewed	A disciplined seam that lets unlike bodies cooperate without swapping internal organs. Shadow: tight coupling and type bleed.
0056	interpreter {Arch}	authored	reviewed	interpreter (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies interpreter, and the review check that would catch drift.
0057	kernel service	authored	reviewed	kernel service names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies kernel service, and the review check that would catch drift.
0058	layer	authored	reviewed	A stratum with a narrow job and limited allowed dependencies.
0059	library	authored	reviewed	library names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies library, and the review check that would catch drift.
0060	listener	authored	reviewed	listener names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies listener, and the review check that would catch drift.
0061	machine boundary	authored	reviewed	machine boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies machine boundary, and the review check that would catch drift.
0062	mediator	authored	reviewed	mediator names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mediator, and the review check that would catch drift.
0063	mesh {Arch}	authored	reviewed	mesh (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mesh, and the review check that would catch drift.
0064	microservice	authored	reviewed	microservice names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies microservice, and the review check that would catch drift.
0065	middleware	authored	reviewed	Cross-cutting logic placed in the path between request and handler.
0066	module {Arch}	authored	reviewed	A package of related definitions meant to travel as one thing.
0067	monolith	authored	reviewed	monolith names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies monolith, and the review check that would catch drift.
0068	namespace {Arch}	authored	reviewed	namespace (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies namespace, and the review check that would catch drift.
0069	node {Arch}	authored	reviewed	node (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies node, and the review check that would catch drift.
0070	observer	authored	reviewed	observer names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies observer, and the review check that would catch drift.
0071	orchestrator	authored	reviewed	A coordinator that sequences many services or tasks into one larger procedure.
0072	package {Arch}	authored	reviewed	package (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies package, and the review check that would catch drift.
0073	pipeline {Arch}	authored	reviewed	pipeline (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies pipeline, and the review check that would catch drift.
0074	platform	authored	reviewed	platform names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies platform, and the review check that would catch drift.
0075	plugin	authored	reviewed	An extension point that lets capability be added without rewriting the host.
0076	port {Arch}	authored	reviewed	port (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies port, and the review check that would catch drift.
0077	presenter	authored	reviewed	presenter names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies presenter, and the review check that would catch drift.
0078	process manager	authored	reviewed	process manager names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies process manager, and the review check that would catch drift.
0079	producer	authored	reviewed	producer names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies producer, and the review check that would catch drift.
0080	projection	authored	reviewed	projection names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies projection, and the review check that would catch drift.
0081	protocol boundary	authored	reviewed	protocol boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies protocol boundary, and the review check that would catch drift.
0082	proxy {Arch}	authored	reviewed	A stand-in that speaks or receives on behalf of another body.
0083	queue {Arch}	authored	reviewed	queue (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies queue, and the review check that would catch drift.
0084	reactor	authored	reviewed	reactor names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies reactor, and the review check that would catch drift.
0085	receiver	authored	reviewed	receiver names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies receiver, and the review check that would catch drift.
0086	registry	authored	reviewed	registry names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies registry, and the review check that would catch drift.
0087	repository {Arch}	authored	reviewed	repository (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies repository, and the review check that would catch drift.
0088	resource boundary	authored	reviewed	resource boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies resource boundary, and the review check that would catch drift.
0089	router {Arch}	authored	reviewed	router (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies router, and the review check that would catch drift.
0090	scheduler	authored	reviewed	scheduler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies scheduler, and the review check that would catch drift.
0091	seam	authored	reviewed	seam names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies seam, and the review check that would catch drift.
0092	service	authored	reviewed	A stable capability exposed for repeated use by others.
0093	service mesh {Arch}	authored	reviewed	service mesh (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies service mesh, and the review check that would catch drift.
0094	session boundary	authored	reviewed	session boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies session boundary, and the review check that would catch drift.
0095	shard {Arch}	authored	reviewed	shard (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies shard, and the review check that would catch drift.
0096	shim	authored	reviewed	shim names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies shim, and the review check that would catch drift.
0097	singleton	authored	reviewed	singleton names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies singleton, and the review check that would catch drift.
0098	source of truth	authored	reviewed	The place other copies are supposed to agree with.
0099	stack {Arch}	authored	reviewed	stack (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies stack, and the review check that would catch drift.
0100	stage {Arch}	authored	reviewed	stage (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies stage, and the review check that would catch drift.
0101	state machine	authored	reviewed	Behavior expressed as named states and legal transitions.
0102	strategy	authored	reviewed	strategy names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies strategy, and the review check that would catch drift.
0103	subsystem	authored	reviewed	subsystem names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies subsystem, and the review check that would catch drift.
0104	surface	authored	reviewed	surface names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies surface, and the review check that would catch drift.
0105	system	authored	reviewed	system names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies system, and the review check that would catch drift.
0106	template method	authored	reviewed	template method names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies template method, and the review check that would catch drift.
0107	tree	authored	reviewed	tree names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies tree, and the review check that would catch drift.
0108	use case	authored	reviewed	use case names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies use case, and the review check that would catch drift.
0109	value object	authored	reviewed	value object names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies value object, and the review check that would catch drift.
0110	worker	authored	reviewed	worker names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies worker, and the review check that would catch drift.
0111	workflow	authored	reviewed	workflow names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies workflow, and the review check that would catch drift.
0112	wrapper	authored	reviewed	wrapper names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies wrapper, and the review check that would catch drift.

97.2 Entries

97.2.1 [0001] abstraction

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A deliberate forgetting of detail so larger structure can be reasoned about without drowning in mechanism.

Shadow: hiding the only failure that matters.

Prompt uses:

• Name abstraction when the prompt needs this obligation made explicit: A deliberate forgetting of detail so larger structure can be reasoned about without drowning in mechanism.
• Ask the assistant to state the abstraction shadow before proposing changes.

Example clause:

Before editing, state the abstraction obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Deliberate forgetting of detail so larger structure can be reasoned about cleanly.

97.2.2 [0002] adapter

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A negotiated translator between unlike shapes. Use it when two systems must meet without infecting one another.

Shadow: adapter jungles that preserve confusion rather than resolve it.

Prompt uses:

• Name adapter when the prompt needs this obligation made explicit: A negotiated translator between unlike shapes. Use it when two systems must meet without infecting one another.
• Ask the assistant to state the adapter shadow before proposing changes.

Example clause:

Before editing, state the adapter obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A translator between unlike shapes that lets systems meet without infecting one another.

97.2.3 [0003] agent {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: agent (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies agent, and the review check that would catch drift.

Shadow: misusing agent at rune 0003 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name agent when the prompt needs this obligation made explicit: agent (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies agent, and the review check that would catch drift.
• Ask the assistant to state the agent shadow before proposing changes.

Example clause:

Before editing, state the agent obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.4 [0004] aggregate {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: aggregate (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies aggregate, and the review check that would catch drift.

Shadow: misusing aggregate at rune 0004 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name aggregate when the prompt needs this obligation made explicit: aggregate (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies aggregate, and the review check that would catch drift.
• Ask the assistant to state the aggregate shadow before proposing changes.

Example clause:

Before editing, state the aggregate obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.5 [0005] anti-corruption layer

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A protective seam that keeps one model from polluting another.

Shadow: misusing anti-corruption layer at rune 0005 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name anti-corruption layer when the prompt needs this obligation made explicit: A protective seam that keeps one model from polluting another.
• Ask the assistant to state the anti-corruption layer shadow before proposing changes.

Example clause:

Before editing, state the anti-corruption layer obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A protective seam that keeps one model from polluting another.

97.2.6 [0006] API gateway

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A threshold that centralizes entry, policy, and routing at the edge of a service world.

Shadow: a convenience chokepoint that quietly becomes a monolith.

Prompt uses:

• Name API gateway when the prompt needs this obligation made explicit: A threshold that centralizes entry, policy, and routing at the edge of a service world.
• Ask the assistant to state the API gateway shadow before proposing changes.

Example clause:

Before editing, state the API gateway obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: An edge threshold that centralizes entry, policy, and routing.

97.2.7 [0007] architecture

Status: canonical

Completion: authored

Semantic status: reviewed

Force: architecture names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies architecture, and the review check that would catch drift.

Shadow: misusing architecture at rune 0007 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name architecture when the prompt needs this obligation made explicit: architecture names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies architecture, and the review check that would catch drift.
• Ask the assistant to state the architecture shadow before proposing changes.

Example clause:

Before editing, state the architecture obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.8 [0008] artifact boundary

Status: canonical

Completion: authored

Semantic status: reviewed

Force: artifact boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies artifact boundary, and the review check that would catch drift.

Shadow: misusing artifact boundary at rune 0008 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name artifact boundary when the prompt needs this obligation made explicit: artifact boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies artifact boundary, and the review check that would catch drift.
• Ask the assistant to state the artifact boundary shadow before proposing changes.

Example clause:

Before editing, state the artifact boundary obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.9 [0009] assembler

Status: canonical

Completion: authored

Semantic status: reviewed

Force: assembler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies assembler, and the review check that would catch drift.

Shadow: misusing assembler at rune 0009 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name assembler when the prompt needs this obligation made explicit: assembler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies assembler, and the review check that would catch drift.
• Ask the assistant to state the assembler shadow before proposing changes.

Example clause:

Before editing, state the assembler obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.10 [0010] backbone

Status: canonical

Completion: authored

Semantic status: reviewed

Force: backbone names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies backbone, and the review check that would catch drift.

Shadow: misusing backbone at rune 0010 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name backbone when the prompt needs this obligation made explicit: backbone names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies backbone, and the review check that would catch drift.
• Ask the assistant to state the backbone shadow before proposing changes.

Example clause:

Before editing, state the backbone obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.11 [0011] backend

Status: canonical

Completion: authored

Semantic status: reviewed

Force: backend names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies backend, and the review check that would catch drift.

Shadow: misusing backend at rune 0011 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name backend when the prompt needs this obligation made explicit: backend names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies backend, and the review check that would catch drift.
• Ask the assistant to state the backend shadow before proposing changes.

Example clause:

Before editing, state the backend obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.12 [0012] boundary

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: The line that says where one responsibility ends and another begins.

Shadow: porous edges that smear blame, ownership, and test scope.

Prompt uses:

• Name boundary when the prompt needs this obligation made explicit: The line that says where one responsibility ends and another begins.
• Ask the assistant to state the boundary shadow before proposing changes.

Example clause:

Before editing, state the boundary obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: The line where one responsibility ends and another begins.

97.2.13 [0013] bounded context

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A protection against semantic bleed: the same word may not mean the same thing in every subsystem.

Shadow: false unification through shared names.

Prompt uses:

• Name bounded context when the prompt needs this obligation made explicit: A protection against semantic bleed: the same word may not mean the same thing in every subsystem.
• Ask the assistant to state the bounded context shadow before proposing changes.

Example clause:

Before editing, state the bounded context obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A semantic fence: the same term is not forced to mean the same thing everywhere.

97.2.14 [0014] bridge

Status: canonical

Completion: authored

Semantic status: reviewed

Force: bridge names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies bridge, and the review check that would catch drift.

Shadow: misusing bridge at rune 0014 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name bridge when the prompt needs this obligation made explicit: bridge names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies bridge, and the review check that would catch drift.
• Ask the assistant to state the bridge shadow before proposing changes.

Example clause:

Before editing, state the bridge obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.15 [0015] broker {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: broker (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies broker, and the review check that would catch drift.

Shadow: misusing broker at rune 0015 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name broker when the prompt needs this obligation made explicit: broker (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies broker, and the review check that would catch drift.
• Ask the assistant to state the broker shadow before proposing changes.

Example clause:

Before editing, state the broker obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.16 [0016] builder

Status: canonical

Completion: authored

Semantic status: reviewed

Force: builder names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies builder, and the review check that would catch drift.

Shadow: misusing builder at rune 0016 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name builder when the prompt needs this obligation made explicit: builder names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies builder, and the review check that would catch drift.
• Ask the assistant to state the builder shadow before proposing changes.

Example clause:

Before editing, state the builder obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.17 [0017] bus {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: bus (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies bus, and the review check that would catch drift.

Shadow: misusing bus at rune 0017 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name bus when the prompt needs this obligation made explicit: bus (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies bus, and the review check that would catch drift.
• Ask the assistant to state the bus shadow before proposing changes.

Example clause:

Before editing, state the bus obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.18 [0018] capability {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: capability (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies capability, and the review check that would catch drift.

Shadow: misusing capability at rune 0018 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name capability when the prompt needs this obligation made explicit: capability (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies capability, and the review check that would catch drift.
• Ask the assistant to state the capability shadow before proposing changes.

Example clause:

Before editing, state the capability obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.19 [0019] channel

Status: canonical

Completion: authored

Semantic status: reviewed

Force: channel names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies channel, and the review check that would catch drift.

Shadow: misusing channel at rune 0019 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name channel when the prompt needs this obligation made explicit: channel names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies channel, and the review check that would catch drift.
• Ask the assistant to state the channel shadow before proposing changes.

Example clause:

Before editing, state the channel obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.20 [0020] client {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: client (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies client, and the review check that would catch drift.

Shadow: misusing client at rune 0020 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name client when the prompt needs this obligation made explicit: client (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies client, and the review check that would catch drift.
• Ask the assistant to state the client shadow before proposing changes.

Example clause:

Before editing, state the client obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.21 [0021] cluster {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: cluster (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies cluster, and the review check that would catch drift.

Shadow: misusing cluster at rune 0021 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name cluster when the prompt needs this obligation made explicit: cluster (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies cluster, and the review check that would catch drift.
• Ask the assistant to state the cluster shadow before proposing changes.

Example clause:

Before editing, state the cluster obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.22 [0022] command bus

Status: canonical

Completion: authored

Semantic status: reviewed

Force: command bus names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies command bus, and the review check that would catch drift.

Shadow: misusing command bus at rune 0022 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name command bus when the prompt needs this obligation made explicit: command bus names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies command bus, and the review check that would catch drift.
• Ask the assistant to state the command bus shadow before proposing changes.

Example clause:

Before editing, state the command bus obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.23 [0023] component {Arch}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A bounded unit of responsibility inside a larger design.

Shadow: misusing component at rune 0023 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name component when the prompt needs this obligation made explicit: A bounded unit of responsibility inside a larger design.
• Ask the assistant to state the component shadow before proposing changes.

Example clause:

Before editing, state the component obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A bounded unit of responsibility inside a larger design.

97.2.24 [0024] composition

Status: canonical

Completion: authored

Semantic status: reviewed

Force: composition names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies composition, and the review check that would catch drift.

Shadow: misusing composition at rune 0024 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name composition when the prompt needs this obligation made explicit: composition names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies composition, and the review check that would catch drift.
• Ask the assistant to state the composition shadow before proposing changes.

Example clause:

Before editing, state the composition obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.25 [0025] connector

Status: canonical

Completion: authored

Semantic status: reviewed

Force: connector names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies connector, and the review check that would catch drift.

Shadow: misusing connector at rune 0025 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name connector when the prompt needs this obligation made explicit: connector names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies connector, and the review check that would catch drift.
• Ask the assistant to state the connector shadow before proposing changes.

Example clause:

Before editing, state the connector obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.26 [0026] container {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: container (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies container, and the review check that would catch drift.

Shadow: misusing container at rune 0026 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name container when the prompt needs this obligation made explicit: container (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies container, and the review check that would catch drift.
• Ask the assistant to state the container shadow before proposing changes.

Example clause:

Before editing, state the container obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.27 [0027] control plane {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: control plane (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies control plane, and the review check that would catch drift.

Shadow: misusing control plane at rune 0027 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name control plane when the prompt needs this obligation made explicit: control plane (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies control plane, and the review check that would catch drift.
• Ask the assistant to state the control plane shadow before proposing changes.

Example clause:

Before editing, state the control plane obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.28 [0028] coordinator

Status: canonical

Completion: authored

Semantic status: reviewed

Force: coordinator names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies coordinator, and the review check that would catch drift.

Shadow: misusing coordinator at rune 0028 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name coordinator when the prompt needs this obligation made explicit: coordinator names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies coordinator, and the review check that would catch drift.
• Ask the assistant to state the coordinator shadow before proposing changes.

Example clause:

Before editing, state the coordinator obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.29 [0029] core {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: core (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies core, and the review check that would catch drift.

Shadow: misusing core at rune 0029 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name core when the prompt needs this obligation made explicit: core (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies core, and the review check that would catch drift.
• Ask the assistant to state the core shadow before proposing changes.

Example clause:

Before editing, state the core obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.30 [0030] coupling

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: The hidden tax paid when change in one place forces change elsewhere. Name it early if you want modularity to survive contact with reality.

Shadow: when a change in one component quietly forces coordinated edits across unrelated surfaces.

Prompt uses:

• Name coupling when the prompt needs this obligation made explicit: The hidden tax paid when change in one place forces change elsewhere. Name it early if you want modularity to survive contact with reality.
• Ask the assistant to state the coupling shadow before proposing changes.

Example clause:

Before editing, state the coupling obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: The hidden tax paid when change in one place forces change elsewhere.

97.2.31 [0031] daemon {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: daemon (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies daemon, and the review check that would catch drift.

Shadow: misusing daemon at rune 0031 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name daemon when the prompt needs this obligation made explicit: daemon (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies daemon, and the review check that would catch drift.
• Ask the assistant to state the daemon shadow before proposing changes.

Example clause:

Before editing, state the daemon obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.32 [0032] data plane {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: data plane (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies data plane, and the review check that would catch drift.

Shadow: misusing data plane at rune 0032 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name data plane when the prompt needs this obligation made explicit: data plane (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies data plane, and the review check that would catch drift.
• Ask the assistant to state the data plane shadow before proposing changes.

Example clause:

Before editing, state the data plane obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.33 [0033] decorator {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: decorator (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies decorator, and the review check that would catch drift.

Shadow: misusing decorator at rune 0033 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name decorator when the prompt needs this obligation made explicit: decorator (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies decorator, and the review check that would catch drift.
• Ask the assistant to state the decorator shadow before proposing changes.

Example clause:

Before editing, state the decorator obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.34 [0034] dependency inversion

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Stable policy should not kneel before unstable detail.

Shadow: concrete dependencies hard-wired into places that should remain portable.

Prompt uses:

• Name dependency inversion when the prompt needs this obligation made explicit: Stable policy should not kneel before unstable detail.
• Ask the assistant to state the dependency inversion shadow before proposing changes.

Example clause:

Before editing, state the dependency inversion obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Stable policy should not kneel before unstable detail.

97.2.35 [0035] dispatcher

Status: canonical

Completion: authored

Semantic status: reviewed

Force: dispatcher names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies dispatcher, and the review check that would catch drift.

Shadow: misusing dispatcher at rune 0035 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name dispatcher when the prompt needs this obligation made explicit: dispatcher names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies dispatcher, and the review check that would catch drift.
• Ask the assistant to state the dispatcher shadow before proposing changes.

Example clause:

Before editing, state the dispatcher obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.36 [0036] domain model

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The conceptual map of the business world the software is trying to serve.

Shadow: misusing domain model at rune 0036 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name domain model when the prompt needs this obligation made explicit: The conceptual map of the business world the software is trying to serve.
• Ask the assistant to state the domain model shadow before proposing changes.

Example clause:

Before editing, state the domain model obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: The conceptual map of the business world the software is trying to serve.

97.2.37 [0037] edge service

Status: canonical

Completion: authored

Semantic status: reviewed

Force: edge service names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies edge service, and the review check that would catch drift.

Shadow: misusing edge service at rune 0037 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name edge service when the prompt needs this obligation made explicit: edge service names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies edge service, and the review check that would catch drift.
• Ask the assistant to state the edge service shadow before proposing changes.

Example clause:

Before editing, state the edge service obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.38 [0038] engine

Status: canonical

Completion: authored

Semantic status: reviewed

Force: engine names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies engine, and the review check that would catch drift.

Shadow: misusing engine at rune 0038 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name engine when the prompt needs this obligation made explicit: engine names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies engine, and the review check that would catch drift.
• Ask the assistant to state the engine shadow before proposing changes.

Example clause:

Before editing, state the engine obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.39 [0039] entrypoint

Status: canonical

Completion: authored

Semantic status: reviewed

Force: entrypoint names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies entrypoint, and the review check that would catch drift.

Shadow: misusing entrypoint at rune 0039 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name entrypoint when the prompt needs this obligation made explicit: entrypoint names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies entrypoint, and the review check that would catch drift.
• Ask the assistant to state the entrypoint shadow before proposing changes.

Example clause:

Before editing, state the entrypoint obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.40 [0040] event bus

Status: canonical

Completion: authored

Semantic status: reviewed

Force: event bus names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies event bus, and the review check that would catch drift.

Shadow: misusing event bus at rune 0040 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name event bus when the prompt needs this obligation made explicit: event bus names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies event bus, and the review check that would catch drift.
• Ask the assistant to state the event bus shadow before proposing changes.

Example clause:

Before editing, state the event bus obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.41 [0041] event handler

Status: canonical

Completion: authored

Semantic status: reviewed

Force: event handler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies event handler, and the review check that would catch drift.

Shadow: misusing event handler at rune 0041 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name event handler when the prompt needs this obligation made explicit: event handler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies event handler, and the review check that would catch drift.
• Ask the assistant to state the event handler shadow before proposing changes.

Example clause:

Before editing, state the event handler obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.42 [0042] executor

Status: canonical

Completion: authored

Semantic status: reviewed

Force: executor names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies executor, and the review check that would catch drift.

Shadow: misusing executor at rune 0042 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name executor when the prompt needs this obligation made explicit: executor names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies executor, and the review check that would catch drift.
• Ask the assistant to state the executor shadow before proposing changes.

Example clause:

Before editing, state the executor obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.43 [0043] facade

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A simplified front door hiding a messier interior.

Shadow: misusing facade at rune 0043 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name facade when the prompt needs this obligation made explicit: A simplified front door hiding a messier interior.
• Ask the assistant to state the facade shadow before proposing changes.

Example clause:

Before editing, state the facade obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A simplified front door hiding a messier interior.

97.2.44 [0044] factory

Status: canonical

Completion: authored

Semantic status: reviewed

Force: factory names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies factory, and the review check that would catch drift.

Shadow: misusing factory at rune 0044 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name factory when the prompt needs this obligation made explicit: factory names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies factory, and the review check that would catch drift.
• Ask the assistant to state the factory shadow before proposing changes.

Example clause:

Before editing, state the factory obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.45 [0045] feature module

Status: canonical

Completion: authored

Semantic status: reviewed

Force: feature module names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies feature module, and the review check that would catch drift.

Shadow: misusing feature module at rune 0045 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name feature module when the prompt needs this obligation made explicit: feature module names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies feature module, and the review check that would catch drift.
• Ask the assistant to state the feature module shadow before proposing changes.

Example clause:

Before editing, state the feature module obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.46 [0046] frontend

Status: canonical

Completion: authored

Semantic status: reviewed

Force: frontend names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies frontend, and the review check that would catch drift.

Shadow: misusing frontend at rune 0046 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name frontend when the prompt needs this obligation made explicit: frontend names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies frontend, and the review check that would catch drift.
• Ask the assistant to state the frontend shadow before proposing changes.

Example clause:

Before editing, state the frontend obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.47 [0047] gateway {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: gateway (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies gateway, and the review check that would catch drift.

Shadow: misusing gateway at rune 0047 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name gateway when the prompt needs this obligation made explicit: gateway (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies gateway, and the review check that would catch drift.
• Ask the assistant to state the gateway shadow before proposing changes.

Example clause:

Before editing, state the gateway obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.48 [0048] graph

Status: canonical

Completion: authored

Semantic status: reviewed

Force: graph names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies graph, and the review check that would catch drift.

Shadow: misusing graph at rune 0048 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name graph when the prompt needs this obligation made explicit: graph names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies graph, and the review check that would catch drift.
• Ask the assistant to state the graph shadow before proposing changes.

Example clause:

Before editing, state the graph obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.49 [0049] handler

Status: canonical

Completion: authored

Semantic status: reviewed

Force: handler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies handler, and the review check that would catch drift.

Shadow: misusing handler at rune 0049 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name handler when the prompt needs this obligation made explicit: handler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies handler, and the review check that would catch drift.
• Ask the assistant to state the handler shadow before proposing changes.

Example clause:

Before editing, state the handler obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.50 [0050] hierarchy {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: hierarchy (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies hierarchy, and the review check that would catch drift.

Shadow: misusing hierarchy at rune 0050 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name hierarchy when the prompt needs this obligation made explicit: hierarchy (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies hierarchy, and the review check that would catch drift.
• Ask the assistant to state the hierarchy shadow before proposing changes.

Example clause:

Before editing, state the hierarchy obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.51 [0051] hook

Status: canonical

Completion: authored

Semantic status: reviewed

Force: hook names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies hook, and the review check that would catch drift.

Shadow: misusing hook at rune 0051 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name hook when the prompt needs this obligation made explicit: hook names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies hook, and the review check that would catch drift.
• Ask the assistant to state the hook shadow before proposing changes.

Example clause:

Before editing, state the hook obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.52 [0052] host

Status: canonical

Completion: authored

Semantic status: reviewed

Force: host names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies host, and the review check that would catch drift.

Shadow: misusing host at rune 0052 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name host when the prompt needs this obligation made explicit: host names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies host, and the review check that would catch drift.
• Ask the assistant to state the host shadow before proposing changes.

Example clause:

Before editing, state the host obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.53 [0053] hub

Status: canonical

Completion: authored

Semantic status: reviewed

Force: hub names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies hub, and the review check that would catch drift.

Shadow: misusing hub at rune 0053 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name hub when the prompt needs this obligation made explicit: hub names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies hub, and the review check that would catch drift.
• Ask the assistant to state the hub shadow before proposing changes.

Example clause:

Before editing, state the hub obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.54 [0054] implementation {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: implementation (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies implementation, and the review check that would catch drift.

Shadow: misusing implementation at rune 0054 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name implementation when the prompt needs this obligation made explicit: implementation (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies implementation, and the review check that would catch drift.
• Ask the assistant to state the implementation shadow before proposing changes.

Example clause:

Before editing, state the implementation obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.55 [0055] interface {Arch}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A disciplined seam that lets unlike bodies cooperate without swapping internal organs.

Shadow: tight coupling and type bleed.

Prompt uses:

• Name interface when the prompt needs this obligation made explicit: A disciplined seam that lets unlike bodies cooperate without swapping internal organs.
• Ask the assistant to state the interface shadow before proposing changes.

Example clause:

Before editing, state the interface obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A disciplined seam that lets unlike bodies cooperate without swapping internal organs.

97.2.56 [0056] interpreter {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: interpreter (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies interpreter, and the review check that would catch drift.

Shadow: misusing interpreter at rune 0056 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name interpreter when the prompt needs this obligation made explicit: interpreter (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies interpreter, and the review check that would catch drift.
• Ask the assistant to state the interpreter shadow before proposing changes.

Example clause:

Before editing, state the interpreter obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.57 [0057] kernel service

Status: canonical

Completion: authored

Semantic status: reviewed

Force: kernel service names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies kernel service, and the review check that would catch drift.

Shadow: misusing kernel service at rune 0057 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name kernel service when the prompt needs this obligation made explicit: kernel service names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies kernel service, and the review check that would catch drift.
• Ask the assistant to state the kernel service shadow before proposing changes.

Example clause:

Before editing, state the kernel service obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.58 [0058] layer

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A stratum with a narrow job and limited allowed dependencies.

Shadow: misusing layer at rune 0058 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name layer when the prompt needs this obligation made explicit: A stratum with a narrow job and limited allowed dependencies.
• Ask the assistant to state the layer shadow before proposing changes.

Example clause:

Before editing, state the layer obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A stratum with a narrow job and limited allowed dependencies.

97.2.59 [0059] library

Status: canonical

Completion: authored

Semantic status: reviewed

Force: library names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies library, and the review check that would catch drift.

Shadow: misusing library at rune 0059 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name library when the prompt needs this obligation made explicit: library names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies library, and the review check that would catch drift.
• Ask the assistant to state the library shadow before proposing changes.

Example clause:

Before editing, state the library obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.60 [0060] listener

Status: canonical

Completion: authored

Semantic status: reviewed

Force: listener names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies listener, and the review check that would catch drift.

Shadow: misusing listener at rune 0060 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name listener when the prompt needs this obligation made explicit: listener names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies listener, and the review check that would catch drift.
• Ask the assistant to state the listener shadow before proposing changes.

Example clause:

Before editing, state the listener obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.61 [0061] machine boundary

Status: canonical

Completion: authored

Semantic status: reviewed

Force: machine boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies machine boundary, and the review check that would catch drift.

Shadow: misusing machine boundary at rune 0061 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name machine boundary when the prompt needs this obligation made explicit: machine boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies machine boundary, and the review check that would catch drift.
• Ask the assistant to state the machine boundary shadow before proposing changes.

Example clause:

Before editing, state the machine boundary obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.62 [0062] mediator

Status: canonical

Completion: authored

Semantic status: reviewed

Force: mediator names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mediator, and the review check that would catch drift.

Shadow: misusing mediator at rune 0062 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name mediator when the prompt needs this obligation made explicit: mediator names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mediator, and the review check that would catch drift.
• Ask the assistant to state the mediator shadow before proposing changes.

Example clause:

Before editing, state the mediator obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.63 [0063] mesh {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: mesh (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mesh, and the review check that would catch drift.

Shadow: misusing mesh at rune 0063 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name mesh when the prompt needs this obligation made explicit: mesh (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mesh, and the review check that would catch drift.
• Ask the assistant to state the mesh shadow before proposing changes.

Example clause:

Before editing, state the mesh obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.64 [0064] microservice

Status: canonical

Completion: authored

Semantic status: reviewed

Force: microservice names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies microservice, and the review check that would catch drift.

Shadow: misusing microservice at rune 0064 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name microservice when the prompt needs this obligation made explicit: microservice names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies microservice, and the review check that would catch drift.
• Ask the assistant to state the microservice shadow before proposing changes.

Example clause:

Before editing, state the microservice obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.65 [0065] middleware

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Cross-cutting logic placed in the path between request and handler.

Shadow: misusing middleware at rune 0065 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name middleware when the prompt needs this obligation made explicit: Cross-cutting logic placed in the path between request and handler.
• Ask the assistant to state the middleware shadow before proposing changes.

Example clause:

Before editing, state the middleware obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Cross-cutting logic placed in the path between request and handler.

97.2.66 [0066] module {Arch}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A package of related definitions meant to travel as one thing.

Shadow: misusing module at rune 0066 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name module when the prompt needs this obligation made explicit: A package of related definitions meant to travel as one thing.
• Ask the assistant to state the module shadow before proposing changes.

Example clause:

Before editing, state the module obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A package of related definitions meant to travel as one thing.

97.2.67 [0067] monolith

Status: canonical

Completion: authored

Semantic status: reviewed

Force: monolith names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies monolith, and the review check that would catch drift.

Shadow: misusing monolith at rune 0067 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name monolith when the prompt needs this obligation made explicit: monolith names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies monolith, and the review check that would catch drift.
• Ask the assistant to state the monolith shadow before proposing changes.

Example clause:

Before editing, state the monolith obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.68 [0068] namespace {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: namespace (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies namespace, and the review check that would catch drift.

Shadow: misusing namespace at rune 0068 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name namespace when the prompt needs this obligation made explicit: namespace (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies namespace, and the review check that would catch drift.
• Ask the assistant to state the namespace shadow before proposing changes.

Example clause:

Before editing, state the namespace obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.69 [0069] node {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: node (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies node, and the review check that would catch drift.

Shadow: misusing node at rune 0069 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name node when the prompt needs this obligation made explicit: node (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies node, and the review check that would catch drift.
• Ask the assistant to state the node shadow before proposing changes.

Example clause:

Before editing, state the node obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.70 [0070] observer

Status: canonical

Completion: authored

Semantic status: reviewed

Force: observer names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies observer, and the review check that would catch drift.

Shadow: misusing observer at rune 0070 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name observer when the prompt needs this obligation made explicit: observer names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies observer, and the review check that would catch drift.
• Ask the assistant to state the observer shadow before proposing changes.

Example clause:

Before editing, state the observer obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.71 [0071] orchestrator

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A coordinator that sequences many services or tasks into one larger procedure.

Shadow: misusing orchestrator at rune 0071 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name orchestrator when the prompt needs this obligation made explicit: A coordinator that sequences many services or tasks into one larger procedure.
• Ask the assistant to state the orchestrator shadow before proposing changes.

Example clause:

Before editing, state the orchestrator obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A coordinator that sequences many services or tasks into one larger procedure.

97.2.72 [0072] package {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: package (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies package, and the review check that would catch drift.

Shadow: misusing package at rune 0072 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name package when the prompt needs this obligation made explicit: package (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies package, and the review check that would catch drift.
• Ask the assistant to state the package shadow before proposing changes.

Example clause:

Before editing, state the package obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.73 [0073] pipeline {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: pipeline (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies pipeline, and the review check that would catch drift.

Shadow: misusing pipeline at rune 0073 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name pipeline when the prompt needs this obligation made explicit: pipeline (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies pipeline, and the review check that would catch drift.
• Ask the assistant to state the pipeline shadow before proposing changes.

Example clause:

Before editing, state the pipeline obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.74 [0074] platform

Status: canonical

Completion: authored

Semantic status: reviewed

Force: platform names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies platform, and the review check that would catch drift.

Shadow: misusing platform at rune 0074 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name platform when the prompt needs this obligation made explicit: platform names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies platform, and the review check that would catch drift.
• Ask the assistant to state the platform shadow before proposing changes.

Example clause:

Before editing, state the platform obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.75 [0075] plugin

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: An extension point that lets capability be added without rewriting the host.

Shadow: misusing plugin at rune 0075 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name plugin when the prompt needs this obligation made explicit: An extension point that lets capability be added without rewriting the host.
• Ask the assistant to state the plugin shadow before proposing changes.

Example clause:

Before editing, state the plugin obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: An extension point that lets capability be added without rewriting the host.

97.2.76 [0076] port {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: port (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies port, and the review check that would catch drift.

Shadow: misusing port at rune 0076 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name port when the prompt needs this obligation made explicit: port (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies port, and the review check that would catch drift.
• Ask the assistant to state the port shadow before proposing changes.

Example clause:

Before editing, state the port obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.77 [0077] presenter

Status: canonical

Completion: authored

Semantic status: reviewed

Force: presenter names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies presenter, and the review check that would catch drift.

Shadow: misusing presenter at rune 0077 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name presenter when the prompt needs this obligation made explicit: presenter names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies presenter, and the review check that would catch drift.
• Ask the assistant to state the presenter shadow before proposing changes.

Example clause:

Before editing, state the presenter obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.78 [0078] process manager

Status: canonical

Completion: authored

Semantic status: reviewed

Force: process manager names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies process manager, and the review check that would catch drift.

Shadow: misusing process manager at rune 0078 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name process manager when the prompt needs this obligation made explicit: process manager names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies process manager, and the review check that would catch drift.
• Ask the assistant to state the process manager shadow before proposing changes.

Example clause:

Before editing, state the process manager obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.79 [0079] producer

Status: canonical

Completion: authored

Semantic status: reviewed

Force: producer names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies producer, and the review check that would catch drift.

Shadow: misusing producer at rune 0079 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name producer when the prompt needs this obligation made explicit: producer names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies producer, and the review check that would catch drift.
• Ask the assistant to state the producer shadow before proposing changes.

Example clause:

Before editing, state the producer obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.80 [0080] projection

Status: canonical

Completion: authored

Semantic status: reviewed

Force: projection names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies projection, and the review check that would catch drift.

Shadow: misusing projection at rune 0080 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name projection when the prompt needs this obligation made explicit: projection names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies projection, and the review check that would catch drift.
• Ask the assistant to state the projection shadow before proposing changes.

Example clause:

Before editing, state the projection obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.81 [0081] protocol boundary

Status: canonical

Completion: authored

Semantic status: reviewed

Force: protocol boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies protocol boundary, and the review check that would catch drift.

Shadow: misusing protocol boundary at rune 0081 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name protocol boundary when the prompt needs this obligation made explicit: protocol boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies protocol boundary, and the review check that would catch drift.
• Ask the assistant to state the protocol boundary shadow before proposing changes.

Example clause:

Before editing, state the protocol boundary obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.82 [0082] proxy {Arch}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A stand-in that speaks or receives on behalf of another body.

Shadow: misusing proxy at rune 0082 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name proxy when the prompt needs this obligation made explicit: A stand-in that speaks or receives on behalf of another body.
• Ask the assistant to state the proxy shadow before proposing changes.

Example clause:

Before editing, state the proxy obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A stand-in that speaks or receives on behalf of another body.

97.2.83 [0083] queue {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: queue (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies queue, and the review check that would catch drift.

Shadow: misusing queue at rune 0083 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name queue when the prompt needs this obligation made explicit: queue (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies queue, and the review check that would catch drift.
• Ask the assistant to state the queue shadow before proposing changes.

Example clause:

Before editing, state the queue obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.84 [0084] reactor

Status: canonical

Completion: authored

Semantic status: reviewed

Force: reactor names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies reactor, and the review check that would catch drift.

Shadow: misusing reactor at rune 0084 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name reactor when the prompt needs this obligation made explicit: reactor names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies reactor, and the review check that would catch drift.
• Ask the assistant to state the reactor shadow before proposing changes.

Example clause:

Before editing, state the reactor obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.85 [0085] receiver

Status: canonical

Completion: authored

Semantic status: reviewed

Force: receiver names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies receiver, and the review check that would catch drift.

Shadow: misusing receiver at rune 0085 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name receiver when the prompt needs this obligation made explicit: receiver names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies receiver, and the review check that would catch drift.
• Ask the assistant to state the receiver shadow before proposing changes.

Example clause:

Before editing, state the receiver obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.86 [0086] registry

Status: canonical

Completion: authored

Semantic status: reviewed

Force: registry names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies registry, and the review check that would catch drift.

Shadow: misusing registry at rune 0086 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name registry when the prompt needs this obligation made explicit: registry names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies registry, and the review check that would catch drift.
• Ask the assistant to state the registry shadow before proposing changes.

Example clause:

Before editing, state the registry obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.87 [0087] repository {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: repository (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies repository, and the review check that would catch drift.

Shadow: misusing repository at rune 0087 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name repository when the prompt needs this obligation made explicit: repository (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies repository, and the review check that would catch drift.
• Ask the assistant to state the repository shadow before proposing changes.

Example clause:

Before editing, state the repository obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.88 [0088] resource boundary

Status: canonical

Completion: authored

Semantic status: reviewed

Force: resource boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies resource boundary, and the review check that would catch drift.

Shadow: misusing resource boundary at rune 0088 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name resource boundary when the prompt needs this obligation made explicit: resource boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies resource boundary, and the review check that would catch drift.
• Ask the assistant to state the resource boundary shadow before proposing changes.

Example clause:

Before editing, state the resource boundary obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.89 [0089] router {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: router (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies router, and the review check that would catch drift.

Shadow: misusing router at rune 0089 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name router when the prompt needs this obligation made explicit: router (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies router, and the review check that would catch drift.
• Ask the assistant to state the router shadow before proposing changes.

Example clause:

Before editing, state the router obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.90 [0090] scheduler

Status: canonical

Completion: authored

Semantic status: reviewed

Force: scheduler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies scheduler, and the review check that would catch drift.

Shadow: misusing scheduler at rune 0090 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name scheduler when the prompt needs this obligation made explicit: scheduler names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies scheduler, and the review check that would catch drift.
• Ask the assistant to state the scheduler shadow before proposing changes.

Example clause:

Before editing, state the scheduler obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.91 [0091] seam

Status: canonical

Completion: authored

Semantic status: reviewed

Force: seam names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies seam, and the review check that would catch drift.

Shadow: misusing seam at rune 0091 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name seam when the prompt needs this obligation made explicit: seam names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies seam, and the review check that would catch drift.
• Ask the assistant to state the seam shadow before proposing changes.

Example clause:

Before editing, state the seam obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.92 [0092] service

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A stable capability exposed for repeated use by others.

Shadow: misusing service at rune 0092 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name service when the prompt needs this obligation made explicit: A stable capability exposed for repeated use by others.
• Ask the assistant to state the service shadow before proposing changes.

Example clause:

Before editing, state the service obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A stable capability exposed for repeated use by others.

97.2.93 [0093] service mesh {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: service mesh (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies service mesh, and the review check that would catch drift.

Shadow: misusing service mesh at rune 0093 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name service mesh when the prompt needs this obligation made explicit: service mesh (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies service mesh, and the review check that would catch drift.
• Ask the assistant to state the service mesh shadow before proposing changes.

Example clause:

Before editing, state the service mesh obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.94 [0094] session boundary

Status: canonical

Completion: authored

Semantic status: reviewed

Force: session boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies session boundary, and the review check that would catch drift.

Shadow: misusing session boundary at rune 0094 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name session boundary when the prompt needs this obligation made explicit: session boundary names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies session boundary, and the review check that would catch drift.
• Ask the assistant to state the session boundary shadow before proposing changes.

Example clause:

Before editing, state the session boundary obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.95 [0095] shard {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: shard (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies shard, and the review check that would catch drift.

Shadow: misusing shard at rune 0095 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name shard when the prompt needs this obligation made explicit: shard (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies shard, and the review check that would catch drift.
• Ask the assistant to state the shard shadow before proposing changes.

Example clause:

Before editing, state the shard obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.96 [0096] shim

Status: canonical

Completion: authored

Semantic status: reviewed

Force: shim names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies shim, and the review check that would catch drift.

Shadow: misusing shim at rune 0096 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name shim when the prompt needs this obligation made explicit: shim names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies shim, and the review check that would catch drift.
• Ask the assistant to state the shim shadow before proposing changes.

Example clause:

Before editing, state the shim obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.97 [0097] singleton

Status: canonical

Completion: authored

Semantic status: reviewed

Force: singleton names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies singleton, and the review check that would catch drift.

Shadow: misusing singleton at rune 0097 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name singleton when the prompt needs this obligation made explicit: singleton names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies singleton, and the review check that would catch drift.
• Ask the assistant to state the singleton shadow before proposing changes.

Example clause:

Before editing, state the singleton obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.98 [0098] source of truth

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The place other copies are supposed to agree with.

Shadow: misusing source of truth at rune 0098 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name source of truth when the prompt needs this obligation made explicit: The place other copies are supposed to agree with.
• Ask the assistant to state the source of truth shadow before proposing changes.

Example clause:

Before editing, state the source of truth obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: The place other copies are supposed to agree with.

97.2.99 [0099] stack {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: stack (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies stack, and the review check that would catch drift.

Shadow: misusing stack at rune 0099 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name stack when the prompt needs this obligation made explicit: stack (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies stack, and the review check that would catch drift.
• Ask the assistant to state the stack shadow before proposing changes.

Example clause:

Before editing, state the stack obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.100 [0100] stage {Arch}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: stage (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies stage, and the review check that would catch drift.

Shadow: misusing stage at rune 0100 in the Arch lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name stage when the prompt needs this obligation made explicit: stage (Arch) names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies stage, and the review check that would catch drift.
• Ask the assistant to state the stage shadow before proposing changes.

Example clause:

Before editing, state the stage obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.101 [0101] state machine

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Behavior expressed as named states and legal transitions.

Shadow: misusing state machine at rune 0101 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name state machine when the prompt needs this obligation made explicit: Behavior expressed as named states and legal transitions.
• Ask the assistant to state the state machine shadow before proposing changes.

Example clause:

Before editing, state the state machine obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Behavior expressed as named states and legal transitions.

97.2.102 [0102] strategy

Status: canonical

Completion: authored

Semantic status: reviewed

Force: strategy names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies strategy, and the review check that would catch drift.

Shadow: misusing strategy at rune 0102 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name strategy when the prompt needs this obligation made explicit: strategy names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies strategy, and the review check that would catch drift.
• Ask the assistant to state the strategy shadow before proposing changes.

Example clause:

Before editing, state the strategy obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.103 [0103] subsystem

Status: canonical

Completion: authored

Semantic status: reviewed

Force: subsystem names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies subsystem, and the review check that would catch drift.

Shadow: misusing subsystem at rune 0103 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name subsystem when the prompt needs this obligation made explicit: subsystem names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies subsystem, and the review check that would catch drift.
• Ask the assistant to state the subsystem shadow before proposing changes.

Example clause:

Before editing, state the subsystem obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.104 [0104] surface

Status: canonical

Completion: authored

Semantic status: reviewed

Force: surface names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies surface, and the review check that would catch drift.

Shadow: misusing surface at rune 0104 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name surface when the prompt needs this obligation made explicit: surface names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies surface, and the review check that would catch drift.
• Ask the assistant to state the surface shadow before proposing changes.

Example clause:

Before editing, state the surface obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.105 [0105] system

Status: canonical

Completion: authored

Semantic status: reviewed

Force: system names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies system, and the review check that would catch drift.

Shadow: misusing system at rune 0105 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name system when the prompt needs this obligation made explicit: system names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies system, and the review check that would catch drift.
• Ask the assistant to state the system shadow before proposing changes.

Example clause:

Before editing, state the system obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.106 [0106] template method

Status: canonical

Completion: authored

Semantic status: reviewed

Force: template method names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies template method, and the review check that would catch drift.

Shadow: misusing template method at rune 0106 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name template method when the prompt needs this obligation made explicit: template method names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies template method, and the review check that would catch drift.
• Ask the assistant to state the template method shadow before proposing changes.

Example clause:

Before editing, state the template method obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.107 [0107] tree

Status: canonical

Completion: authored

Semantic status: reviewed

Force: tree names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies tree, and the review check that would catch drift.

Shadow: misusing tree at rune 0107 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name tree when the prompt needs this obligation made explicit: tree names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies tree, and the review check that would catch drift.
• Ask the assistant to state the tree shadow before proposing changes.

Example clause:

Before editing, state the tree obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.108 [0108] use case

Status: canonical

Completion: authored

Semantic status: reviewed

Force: use case names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies use case, and the review check that would catch drift.

Shadow: misusing use case at rune 0108 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name use case when the prompt needs this obligation made explicit: use case names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies use case, and the review check that would catch drift.
• Ask the assistant to state the use case shadow before proposing changes.

Example clause:

Before editing, state the use case obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.109 [0109] value object

Status: canonical

Completion: authored

Semantic status: reviewed

Force: value object names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies value object, and the review check that would catch drift.

Shadow: misusing value object at rune 0109 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name value object when the prompt needs this obligation made explicit: value object names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies value object, and the review check that would catch drift.
• Ask the assistant to state the value object shadow before proposing changes.

Example clause:

Before editing, state the value object obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.110 [0110] worker

Status: canonical

Completion: authored

Semantic status: reviewed

Force: worker names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies worker, and the review check that would catch drift.

Shadow: misusing worker at rune 0110 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name worker when the prompt needs this obligation made explicit: worker names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies worker, and the review check that would catch drift.
• Ask the assistant to state the worker shadow before proposing changes.

Example clause:

Before editing, state the worker obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.111 [0111] workflow

Status: canonical

Completion: authored

Semantic status: reviewed

Force: workflow names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies workflow, and the review check that would catch drift.

Shadow: misusing workflow at rune 0111 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name workflow when the prompt needs this obligation made explicit: workflow names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies workflow, and the review check that would catch drift.
• Ask the assistant to state the workflow shadow before proposing changes.

Example clause:

Before editing, state the workflow obligation, the evidence that satisfies it, and the failure mode if it is missing.

97.2.112 [0112] wrapper

Status: canonical

Completion: authored

Semantic status: reviewed

Force: wrapper names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies wrapper, and the review check that would catch drift.

Shadow: misusing wrapper at rune 0112 in the architecture lane can let ownership can blur across layers; verify by requiring the caster to name the owning artifact and the caller-visible contract.

Prompt uses:

• Name wrapper when the prompt needs this obligation made explicit: wrapper names a concrete architecture and design obligation: separate responsibility, boundary, and interface decisions. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies wrapper, and the review check that would catch drift.
• Ask the assistant to state the wrapper shadow before proposing changes.

Example clause:

Before editing, state the wrapper obligation, the evidence that satisfies it, and the failure mode if it is missing.