/cognitive-maps/the-set

The set, at a glance

Every page earns one picture, drawn from the data model — the whole argument seen at once, before you walk it.

Start here · the whole argument in motion

One image carries the value proposition; the rest of the set elaborates its parts. The append-only event ledger sits at the base, and the cognitive map materializes out of it in event order — scrub it, or replay. Regions forming, typed edges, lineage risers, the late flip to stale: everything the plates below show precisely is already here, derived from the events and nothing else. Start with this; then walk the readings.

12 · shape_materialized_event_id
The event ledger rising into a cognitive mapAn append-only ledger at the base; events rise off it into a graph of resource-nodes and typed edges that gain opacity with recency; two region glows converge while an isolate stays separate and a superseded node ghosts behind.PROJECTION · MATERIALIZED AT READ TIME · THE GRAPH RISES AS THE LEDGER GROWS“first-week confidence”converged · salience high · cohesion tight · ≈3 fogged“deployment”forming · bound by facet, not contenttelos chartergenesis_event_idpair-on-first-PRstagingregulationsolo-retrono facet · no edgecogmap_seededresource_createdresource_createdrelationship_assertedrelationship_assertedresource_createdresource_createdresource_createdrelationship_assertedresource_createdregion_materializedregion_materializedrelationship_reweightedtime →kb_eventsthe source of truth — append-onlyemitter_entity_id · event_type_id · payload · producing_anchor_* · occurred_atexpresscontainsleads_tonearfolded / supersededopacity = recency
Shown from the schema

Six pages that argue from the data model outward — the visuals are the evidence.

“first-week confidence”SALIENCEhigh≈ 7 members · identities withhelda region forming
What a cognitive map is

A map's honest shape — regions with weight and population, members fogged.

resourceskb_resourcesgenesis_event_idcontent blockskb_content_blockslast_event_idedgeskb_edgesasserted_by_event_idpropertieskb_propertieslast_event_idcogmap-regionskb_cogmap_regionsgenesis_event_idPROJECTIONS · DERIVED, REPLAYABLEKERNEL · CONVENTION-AGNOSTICevents · entities · resources · edges · properties · blocksworkflow / KB · cognitive map — neither baked inkb_eventsthe source of truth — append-onlytime →emitter_entity_id · event_type_id · producing_anchor_* · correlation_id
The substrate beneath it

Events are primary; every surface is a projection over the ledger.

RESOURCE · atomic, graph-participatingCONTENT-BLOCK · addressable interiortelos_resource_idexpressresource_idcontains · 1 → Nkb_cogmapsname = onboardingtelos_resource_id ↘kb_resourcesthe chartertitle · origin_uribody_hash (merkle over its blocks)stands alone · anchors edges & propertieshomed in the mapkb_resourceslabel =operationalized_by“pair on the first PR”kb_propertiesdoc_type = "cogmap_charter"kb_content_blocksthe questionsresource_id → charter · seq · is_foldedgenesis_event_id · last_event_idseq 0 = the telos statementseq ≥ 1 = the guiding questionseach a projection of its own event streamWHY TWO?a resourcestands in the graph;a block is addressableinside one, andattributable on its own.
What lives in a map

Two primitives — a resource stands in the graph; a block is its addressable interior.

THE LEDGERevent · refevent · mergeevent · backfirewatchessteward agentpersona · stewardloads charter + regulationWHAT IT READSresource_body_textresource_blockscogmap_regulationrelevant tothis telos?A LEARNING-ACTformnew concept or relation · STOREmodifyreinforce · DERIVED, not storeddecaystanding falls · RESTRAINTfoldis_folded · preserved, not wrongscarfold the blockand write regulationprovenance → folded blockregulation resource“pair on the first PR”writes forwardevery act emits provenance-with-stanceemit → kb_block_provenancegrowth is a loop
How a map grows

Five learning-acts — form, modify, decay, fold, and the scar that stays.

BOUNDARYside-map(team-a)“sprint rituals”SALIENCEhigh≈ 7 members · interior stays homeshape →team-b map“sprint rituals”salience high · ≈ 7seen, not read
How maps relate

Shape crosses a boundary; the material interior stays home.

epd-department map“good sprint process”PROPOSED · homed in departmentactor · member on both sidescurates send-forward eventsend-forwardrelates back ↓ (referenced, not copied)side-map(team-a)“sprint rituals”SALhighteam-b map“sprint rituals”SALhighmutual high salience = signal ↑
How maps relate

Promotion — a curated concept sent forward across scopes (proposed).

THE SEED · SIX TEAMStemper-systemorg-commonepd-departmentdirectorsepd-team-aepd-team-bevery team descends from the rootVISIBILITY = PERMISSION × PRECEDENCEpermissionwhat's in your set — down the DAGprecedencewithin it — what rankstwo independent answers
What's visible from here

The teams DAG, and visibility = permission × precedence.

ONE MAPthe shaperegions · salience · countsthe resourcesthe material insideGATE 1 · SHAPE-READABILITY“are you a member of a teamjoined to this map?”cogmap_readable_by_profile()GATE 2 · GRANT-INHERITANCE“has a resource been grantedto a team you reach?”resources_visible_to()different questions · different functions · different answers
What's visible from here

Two gates, kept apart — reading a shape vs reading resources.

An invitation · operating Temper

What a deployment shapes, argued toward decisions not yet made.

DEPLOYMENT-SHAPE RANGE · YOURScluster · operated DBmulti-tenant + per-tenant webhooksdedicated agent infraserverless · Neon · single-tenantplatform agents▸ temperkb.io · one point near the minimum0emptyPostgresschemaloadedTemper servingCLI / API / MCP1“this is the seed file”temper-system · system-defaultINVARIANT · SOLIDN · a new map by authoringN · a webhook stream arrivingN · an agent waking…the shape opens here
Deployment

0→1 is the invariant seed; topology, tenancy, and agents are the org-shaped range.

AUTHORINGBUILTcogmap_genesisa new map, inside the boundariesADMINISTRATIONPROPOSED · ORG-SHAPEDreshape the access graphprofiles · teams · DAG · team↔mapminimalguarded · SAMLeventeventkb_eventsone ledger · emitter + producing anchorBUILTcognitioncogmaps · subscriptions · relationshipscompliance-audit streamprivacy- & auth-bound · kept for complianceFIREWALLa grant is not a conceptPOSTGRES RESPONSIBILITY BOUNDARYthe ledger stops herea direct command can bypass the ledger
Governance & administration

Administration is event-sourced — and firewalled from cognition.

INSIDE · THE EVENT LEDGERbuilt · the audit you get for freeEpistemichow understanding formedassertfoldreinforcescarfeeds the mapsGovernancewho was granted what, whengrantrevokecompliance · firewalleddoes not feed the mapsOUTSIDEproposed · external toolingOperationalis the system healthycallslatencyerrorsOpenTelemetryPrometheuswhich metrics:an org-scoped dialemitPOSTGRES RESPONSIBILITY BOUNDARYbelow: direct database commands — outside the ledger entirely
Observability & audit

Two audits, two homes — operational outside, epistemic in the ledger.

GITHUBTEMPER · the cognitive substratecorrelation_id — one thread, end to endPR #123mergedREMOTE ACTwebhook eventcarries correlation idagentwakesREADS CHARTERmutationeventreasoning in payloadmetadata jsonbwrites aregulationreinforcesa questionreinforce_count ++ANALYTICS DASHBOARDquery the provenance: why did our understanding of onboarding shift this week?proposed
Insights

A causal chain from a merge to a shift in a map’s understanding.