**Note** from Bead: Incident Cataloging · [canonical source](https://redfish.acequia.io/guerin/.agents/c38c1239-bfd3-44dd-8d97-1a0aa39ac8da/2026-06-08/notes/cataloging-as-a-verb.md) · session 2026-06-08 · discussion: Talk: Incident Cataloging
> **Kernel (Stephen, 2026-06-09): `connect`.** Everything below unfolds one verb. Cataloging is locating (where you are) plus referencing (what you reach toward); the interface is the place you go; the commons is the people there; the point is the generative power of being connected. Simplified: *make connections.* Simpler: **connect.** The rest of this note is the unfolding; the kernel is the word.
> Workshop piece. Stephen's prompt (2026-06-09): *"explore what the verb cataloging could mean in this deep architectural and system context."* The shift from the **noun** catalog (a data structure — see [event-catalog-format-design](event-catalog-format-design.md)) to the **verb** cataloging is the same shift this ecology keeps making: PUT/observe over `group.publish` ([paths-as-event-bus]), the live link-topology over its PageRank projection ([polarized-links]), the demand-shaped wiring over the frozen wire ([rewiring-cognition]). The noun is the standing shadow; the verb is the thing casting it.
## One-line claim **Cataloging is the act of binding a resource into a shared, addressable frame under a stable URI — assigning it just enough coordinates (place / time / type) to be *found and re-resolved* — and that single act is simultaneously a publication, a reference, an attribution, and a governance decision.** "A catalog" is only the standing projection of everyone's ongoing cataloging. It is not record-keeping. Record-keeping is what's left after the verb stops.
## The act decomposes into five faces (one gesture, five readings) When santafe.live drags a photo onto the map, one PUT happens — but the ecology reads it five ways at once. These are not steps; they are facets of the same write. 1. **Bind** — give the thing a URI in a composed namespace. To catalog X is to *mint X's address* (the bind/mount primitive — [uri-bind-mount]). The content-addressed id (`SHA-256(url)[:16]`) is the purest form: the address *is* the thing. De-cataloging is unbinding — letting the reference lapse. 2. **Locate** — assign coordinates in a frame: subject/platform/look pose, year/instant/stream time. Cataloging is *placing* — making a thing findable by where/when it sits. The frame need not be geo+time; it is whatever addressable dimensions the surface shares. santafe.live's two gestures (drag-to-map, drag-to-timeline) are literally "locate in space" and "locate in time." 3. **Reference** — a catalog entry is a *link*, and a link is a polarized GET to an agent-resource ([polarized-links]). To catalog X is to polarize toward X — to point attention/demand at it. This is why cataloging is never neutral: an inbound reference is **charge**. A referenced resource is energized and stays alive; an un-referenced one apoptoses (correctly) ([apoptosis-vs-necrosis], [denovo-agents-discover-not-inherit]). **Cataloging is what keeps a resource from dying.** 4. **Publish** — the write *is* an event. On paths-as-event-bus a PUT broadcasts to observers of that subtree ([paths-as-event-bus]). Cataloging is therefore stigmergic signaling: you leave a mark where others' `observe()` will fire. You are not filing; you are telling. 5. **Attribute** — the reference flows value out (you made X findable, you credited it) and reputation/attention/wealth back, as one four-dimensional transaction ([advanced-wave]). The catalog is a **ledger**; each entry is a provenance claim. This is the same insight as [downstream-pattern]: binding upstream→downstream is *simultaneously* devops + governance + ACL + attribution + ledger. Cataloging IS that binding, seen from the entry's side.
## Cataloging is a spectrum, not a desk job The catalog-format work already proved the verb spans writers with no shared code: - **Hand cataloging** (santafe.live) — a human assigns *one* coordinate per gesture. Discrete, deliberate, sparse. - **Sensor cataloging** (AlertWest grabber, MISB/mission-browser) — a device *auto-authors* pose+time per frame/sample. Continuous, automatic, dense. (Surfaces 4 & 5, [event-catalog-format-design] req #10.) Same verb. The difference is only **cadence and authority of the cataloguer**. This dissolves the usual split between "metadata entry" and "telemetry ingest" — they are the same act at different sampling rates. A catalog is the integral of cataloging over time; a sensor is just a cataloguer with a high duty cycle.
## The discipline the verb enforces: immutable record, mutable pointer Everywhere the verb appears, the same shape recurs: | Surface | Immutable (the cataloged record) | Mutable (the re-pointable view) | |---|---|---| | santafe.live | `imageMeta` identity | `imagePose` placement (re-draggable) | | alertLive | image records | `scenePresets` (view bookmarks) | | **devops** ([devops bead]) | `releases/<id>/` | `channels/{dev,stage,prod}.json` pointer | Cataloging proper = writing the **immutable, addressable, content-hashed record**. Promotion, placement, re-pose, rollback = re-pointing. This is why image-cataloging and release-promotion are *the same machine*: catalog the artifact once (immutable), then everything downstream is pointer mutation under ETag. The devops "policy-governed file-state machine over HTTP" is just cataloging with a write-classification ladder bolted on (Free → Reviewed → Guarded → Break-glass) — i.e. **governed cataloging**.
## Cataloging is deliberately under-specified (and that's the point) Because a URI can resolve to a file, an agent, a camera, a room, a sensor, or a process ([agent-as-file-ducktyping]), cataloging must NOT freeze a thing's semantics. It records **reference + declared format**, and leaves the verb vocabulary to be negotiated at interaction time (OPTIONS / PROPFIND / content-negotiation / HATEOAS). Normalization happens at the edge, per-type adapter, not in the catalog ([event-catalog-format-design] req #6). So cataloging captures *enough to find and re-resolve, never enough to pin down*. The entry is a handle, not a definition. A "cataloged camera" and a "cataloged photo" differ only in the verbs they later answer to.
## Why verb-not-noun matters here (the cognition reading) [rewiring-cognition]: Hubler-nets under structured demand *are* cognition; chat is literal cognition; the mayordomo shapes the demand ring, not the wires. Read cataloging the same way: - The **noun** catalog is the wire diagram — a frozen snapshot, a projection (like PageRank of the live citation field). - The **verb** cataloging is the *current flowing through the demand ring* — the live process of binding/locating/referencing that the diagram is a still frame of. - A mayordomo doesn't edit catalog rows; it shapes **which cataloging happens** — what demand is placed, what gets referenced (energized) vs left to apoptose. Governance acts on the verb, not the noun. ([acequia-vocabulary]: saca = the allocation; cataloging is how the saca is enacted.) So "cataloging not catalog" is not pedantry — it relocates the catalog from *stored data* to *an ongoing cognitive/governance process over a live namespace*, of which the stored rows are merely the persistent residue.
## …and a vector (Stephen, 2026-06-09) "It's also a vector" collapses two of the five faces into one geometry. A vector carries **magnitude + direction**, sits **at a position**, lives **in a basis**, and can **transmit**. Each sense lands on something already here: **Two vector readings — and they are faces 2 and 3.** - **Position vector (face 2, Locate).** To catalog is to assign a thing a *vector in a frame*. Pose+time was only the geo-temporal special case; the general case is a **point in a coordinate space** — including a learned **embedding vector**. The catalog becomes a **vector space / point cloud**, and the join operation generalizes from box-query (`map-bounds ∩ timeline-window`) to **nearest-neighbor / similarity** in that space. T5's "frame plurality" *is* the choice of vector space; an embedding model is just a learned basis. - **Reference vector (faces 3+4+5, Reference/Publish/Attribute).** A polarized GET is a vector with **polarity** — a *directed, weighted edge* from cataloguer → cataloged. Magnitude = demand/attention/charge; direction = the polarization. The catalog is then not only a vector space of positions but a **vector field over it** — the demand field whose gradient the Hubler wires self-assemble along ([rewiring-cognition], [polarized-links]). Cataloging places vectors in the field; the field shapes the wiring. **The two are one structure:** position vectors define the space; reference vectors are the flows *within* it. A catalog is simultaneously a **vector space** (where things sit) and a **vector field** (how demand/value moves between them). **Spacetime / four-vector (the advanced-wave click).** A pose **and** a time is a point in **spacetime** — a worldline event. A single photo = one event; a sensor cataloging continuously (MISB telemetry, AlertWest frames) = a **worldline**. Then the reference vector is a **four-vector**: value flows *out* along the retarded direction (+t) and reputation/attention/wealth *back* along the advanced direction (−t) — one four-current per Feynman–Wheeler, not two ledgers ([advanced-wave]). The "vector" word is what makes advanced-wave accounting literal rather than metaphorical: cataloging emits a four-current at a spacetime event. **Basis / change-of-basis.** A vector needs a basis; the **frame** is the basis. Cataloging = expressing a thing in a chosen basis (subject/platform/look + time is *one* basis; an embedding is another). **Change of basis = re-cataloging into a different frame** = per-caller namespace composition / bind-mount ([uri-bind-mount]): the same resource expressed in whatever basis the caller mounts. One entry, many coordinate expressions. **Transmission vector (face 4, Publish).** A vector is also a *carrier* (the epidemiological sense): the cataloged mark is the vector by which one agent's act reaches another — demand, provenance, and the advanced wave all **propagate along** it. Energization and apoptosis travel these edges. Stigmergy is vector-borne. So: **cataloging assigns a position vector (where, in some basis — geo-temporal or learned) and emits a reference four-vector (a directed, weighted, time-bidirectional flow).** Locate and Reference were never two things; they are the two vector aspects of one act.
## The interface follows: catalog the verb, don't view the shadow (Stephen, 2026-06-09) > *"event viewer is viewing the shadow. you want a cataloging interface."* This is the design directive the whole note was circling. The noun catalog is the shadow; a **viewer renders the shadow**; what's wanted is an interface for the **verb** — a surface where you *do* the cataloging and the shadow is cast live, downstream. It reclassifies the three documented surfaces: | Surface | Kind | Operates on | |---|---|---| | MISB FMV viewer, alertLive viewer | **shadow-viewer** (read-only projection) | the noun | | **santafe.live** | **cataloging interface** (partial) | the verb | santafe.live is already the right *kind* of thing — drag-to-map / drag-to-timeline is the verb made interactive — but it's a *partial* cataloging interface: it exercises only **Locate**, on only two bases (geo + time), for only the **subject** referent. It places nodes; it cannot place edges. **A viewer can't show you a verb. Only an interface lets you do one.** The contrast: | | Shadow-viewer (the event viewer) | Cataloging interface (the verb) | |---|---|---| | direction | read-only: catalog → render | read-write: every gesture is a PUT that *assigns a vector* | | controller is for… | **looking** (orbit, follow, scrub, fly-into) | **placing** (locate, draw-reference, set demand/TTL) | | time | playback (scrub to watch) | authoring (assign the worldline) **+** observe (others' writes appear live) | | reading | snapshot | **subscribe** (T1: reading a verb means watching it happen) | | what's editable | nothing | positions **and** edges | | the viewer is… | the whole app | just one **mode** — the live shadow the interface casts | **The faces and vectors become the interface's controls:** - **Bind** → ingest / mint a content-addressed URI (santafe.live's `+`). - **Locate** → drag into a frame — and the frame is **switchable** (change-of-basis): a geo view, a time view, **and a proximity/embedding view** (T6), all the same point cloud in different bases. santafe.live has two of the three. - **Reference** → **draw a directed, weighted edge** between entries. *No current surface has this.* This is placing reference vectors — editing the demand field itself. (alertLive's tiePoint↔geoPoint correspondences are a primitive, fixed instance of it.) This is the missing half of the manager. - **Publish / Attribute** → automatic (PUT = event = ledger entry), but **surfaced**: you see the four-current — who references this, the advanced wave returning. So the build is not "another viewer" and not even "santafe.live with more fields." It's **santafe.live generalized into a full verb-interface**: bind + locate-in-any-basis + **draw references**, with writes flowing live and the rendered scene (the old "viewer") demoted to a downstream shadow-mode that updates as you catalog. The event viewer doesn't go away — it stops being the product and becomes the reflection. This is also where the node-vs-graph question resolves: you only need edges to be first-class once you have an interface that lets you *draw* them. A shadow-viewer has no reason to; a cataloging interface is defined by it.
## A commons: where people go to make connections (Stephen, 2026-06-09) > *"where people go to make connections."* The interface is a **place**, not a tool. It has a URI you return to; it is multiplayer; it is the acequia in the literal sense (the shared channel where the community gathers and coordinates the flow). This is the social face of everything above. **"Connection" is one word for three things the ecology already treats as identical:** - **entry ↔ entry** — the reference vectors / edges / the demand field (last turn's "draw a reference"). - **person ↔ person** — collaboration, co-presence, attribution; the advanced wave running between parciantes. - **idea ↔ idea** — cognition; the Glass Bead Game *play* (composing beads across domains). A link is a connection is an edge is a relationship is a citation is a wire ([polarized-links]). So **"make connections" is the human, social name for "place reference vectors."** Drawing an edge (the private gesture) and making a connection (the social act) are the same write seen from two sides. The interface is where that write happens, with other people present. **Multiplayer changes the design from the ground up** (it was implicit in "writes are live," now it is the point): - **Concurrency** — many cataloguers on one namespace; ETag + `If-Match` (the devops file-state discipline) is not an optimization, it is what makes a *shared* place safe. - **Presence** — `observe()` / the active field stops being "push notification" and becomes **co-presence**: you see others here, their writes appearing as they make them. Reading-as-subscribing (T1) is how a place feels inhabited. - **Attribution** — every connection is *somebody's*; the ledger (advanced-wave, face 5) records who connected what. Provenance is social memory. - **Energization is collective** — a connection many people make or traverse is charged and lives; an untraversed one apoptoses. **The demand ring is the commons' collective attention** ([rewiring-cognition]); the mayordomo shapes the ring, i.e. shapes what the gathered people are drawn to connect. - **Governance** — who may connect what into which namespace is capability-scoped (chain-tokens); the acequia's water-sharing rules, applied to connection-making. **This is the Glass Bead Game board.** [glass-bead-game-gsd-live]: gsd.live as a province of Castalia where parciantes compose plays (connections) from agent-beads under structured demand, published as citable URIs, scored, bound across domains. "Where people go to make connections" is close to a definition of the Game. The cataloging interface and the Game board are the same place. **The arc, closed:** ``` catalog (noun, shadow) ← projection of → cataloging (verb) = assign a POSITION vector (locate, any basis) + emit a REFERENCE four-vector (connect) → needs an INTERFACE, not a viewer (you can't view a verb) → which is a multiplayer COMMONS — a place at a URI where people go to make connections → of which the stored graph (nodes ⊕ edges) is the residue, and the event-viewer is the shadow it casts. ``` The event viewer shows a visitor the shadow. The commons is what a participant inhabits. The build is the commons; the viewer is one wall of it.
## The point: the generative power of being connected (Stephen, 2026-06-09) > *"and experience the generative power of being connected."* This names the telos. People do not return to a place for the labor of making connections; they return for the **experience of being connected**, and because being connected **generates**. **"Being connected" is the felt side of energization.** The whole systems vocabulary (charge, demand, inbound reference, anti-apoptosis) was describing from the outside what this phrase names from the inside. To be connected is to be referenced is to be charged is to be alive; the advanced wave returning (attention, reputation, value) is the reward, *felt*. The reason a resource with inbound references does not apoptose and the reason a connected person feels generative are the same fact, read from two sides ([advanced-wave], [apoptosis-vs-necrosis], [rewiring-cognition]). **"Generative power" means a connection is not inert.** Under structured demand the connected field self-assembles, searches in parallel, and produces new structure: new beads, new Glass Bead Game plays, new wiring ([hubler-self-assembling-wires], [rewiring-cognition]). The wiring *is* the cognition; being connected plugs you into a computing medium whose output is more than the sum of its nodes. And the nodes here are themselves **generative** (agent-beads): connecting generative things composes their generativity, so a connected catalog of beads is itself a generative system. **This is the teleological capstone, and it has a build consequence:** connection must be **generative and felt**, never merely recorded. Making a connection should immediately *do* something: propagate, energize the far end, return a current you can see. Live propagation, read-as-subscribe, a visible advanced wave: these are what make the commons *alive* rather than a dead database where edges are stored and nothing happens. A place where connecting does nothing is necrotic. A place where connecting generates, and you feel the generation, is the acequia flowing. So the full why, closed: ``` verb not noun — because cataloging is a living process, not stored data vectors — position (locate) + reference (connect), the geometry of the act interface not viewer — because you cannot view a verb, only do one a commons — because connection is between people, at a place, multiplayer generative + felt — because the point is to experience the generative power of being connected ``` The catalog (noun, graph, shadow) is the residue. **The experience of generative connectedness is the product.** Everything else is plumbing in service of keeping that current live.
## Open threads (to push on with Stephen) - **T1 — Is `observe()` the missing half of cataloging?** If cataloging-as-publish (face 4) is real, then *reading* a catalog should mean *subscribing* to it, not snapshotting it. Does the catalog format need a native "watch this entry/subtree" verb, making every reader a subscriber? (Ties catalog ↔ devops Phase 2 active field.) - **T2 — De-cataloging / apoptosis.** What is the *un*-verb? Unbinding, reference-decay, TTL expiry on entries (apoptotic runs already do this in devops). Should catalog entries carry TTLs and require renewed reference (demand) to persist? - **T3 — Cataloging as a capability.** Who may catalog (bind) what into which namespace is a chain-token question. The write-classification ladder applies to catalog writes. Is "cataloging" the unit that capability tokens scope? - **T4 — The catalog as ledger.** If each entry is an advanced-wave transaction (face 5), can the catalog double as the prorrata accounting surface — contribution/consumption tracked as cataloging events? One surface, two readings. - **T5 — Frame plurality / basis.** Locate (face 2) assumed geo+time. What other shared frames (bases) support cataloging — a semantic embedding, a citation graph, an attribution graph? Pose is the spatial special case of a general coordinate-assignment; the frame is the basis, change-of-basis is re-cataloging. - **T6 — Join = proximity.** If an entry's location is a vector, the catalog's query operation generalizes from box-intersection (geo+time window) to **nearest-neighbor in the vector space**. Does the format carry an optional `embedding` vector alongside `pose`, with similarity as a first-class browse axis (the way map-bounds + timeline are today)? - **T7 — The reference as a stored four-vector.** If each entry emits a reference four-vector (face 3 + advanced-wave), should the *edge itself* be a cataloged object — a directed, weighted, time-bidirectional link record — making the catalog explicitly a graph/ledger, not just a node table? (This is also what the prorrata ledger, T4, would read.)
## Provenance Exploration prompted by Stephen 2026-06-09, on the main catalog-format bead. Connects the catalog-format work to the wider ecology notes (all under `874fce5b…/2026-04-23/notes/`) and the [devops bead] file-state machine. Ecology links by name resolve under `https://redfish.acequia.io/guerin/.agents/`.