> The named pains from the previous act tell you where the bleeding is. This act draws the boundaries that decide what would stop it. The pains and their knowledge are clustered into bounded domains; each domain is classified (Core, Supporting, or Generic), profiled (who creates and consumes it, how volatile, the cost of it being wrong), and given a quality bar - what it must do, for whom, at what cost if it fails. Then the domains are *related* - the typed edges between them - because the expensive pains live where knowledge crosses a boundary, not inside one. > > Requirements first, tool decisions last. ^purpose 1. We cluster the trail's pains and knowledge into bounded domains - the boundary is where the language changes 2. We classify each domain Core / Supporting / Generic - the lever that later decides centralise vs. keep-and-own 3. We profile within each: who creates and consumes it, how volatile, and a quality bar - what it must do, for whom, at what cost if it fails (rare high-consequence [[Decision record|rationale]] and ambient procedural know-how cannot share one method) 4. We map between: draw the typed edges and name each one's **edge-property** (common demand, directed dependency, model mismatch, ...) from the [[Context Mapping]] vocabulary - who supplies whom, where knowledge crosses a silo; the cross-domain edges are the costly ones 5. We name a steward per domain - requirements without named ownership are aspirations ^plan The informal brokers identified during the previous act are the natural candidate stewards for the domains they already serve. **You leave with:** - A bounded domain per cluster, each classified Core / Supporting / Generic - A quality bar per domain - what the knowledge must do, and which requirements are non-negotiable - A context map - each edge named by its edge-property, with the cross-silo ones flagged as the costly pains - A first pass at stewardship - who already does the work informally, surfaced and named ^outcomes ## General taxonomy The artefact this act produces, in general-KM form — pains and the attributes whose absence each one indicates, without per-engagement clustering: ![[Knowledge pain to attribute map#^table]] ## Examples of clusters profiled here 1. [[Second brain example - personal notes|Second brain (personal notes)]] ![[Second brain example - personal notes#^profile-line]] 2. [[Shared second brain example - ADR log|Shared second brain (ADR log)]] ![[Shared second brain example - ADR log#^profile-line]] 3. [[Shared second brain example - Expertise Radar|Shared second brain (Expertise Radar)]] ![[Shared second brain example - Expertise Radar#^profile-line]] 4. [[Shared second brain example - Experts Hub|Shared second brain (Experts Hub)]] ![[Shared second brain example - Experts Hub#^profile-line]]