Knowledge workspace

Explore records, relationships, and room structure in the same room.

Find records

Records shows the active room’s standard inventory, excluding archived decisions. Search full titles or identifiers and filter by type and status. Explicitly include inherited content when needed; only then is the origin column shown. New record and Import are in the inventory header, with import jobs beside them. Previous and Next in detail move only through the current results; both are disabled outside that list. Back to records and browser Back preserve room, query, filters, and list position. An unspecified status is not approval.

The editor

Clicking a file opens it in the editor, laid out in two columns: the metadata (key, status, who decided, dates, properties, tags, related records, lifecycle) plus the associations and citing runs on the left, and the formatted body on the right. Drafts are directly editable and save automatically. Accepted records are read-only because governance seals them once decided. Rules open here too, read-only, with their statement, enforcement, and exceptions. You don’t need a separate page for them.

Wikilinks connect knowledge: a “[[KEY]]” in a body renders as a link and jumps to that record. On the left, below the metadata, you find the record’s associations (references and backlinks like “supersedes” or “depends on”) and the chat runs that cited it.

Relationships and room structure

Relationships shows decisions, rules, and documents in the readable room inventory. Its count includes only inspectable typed relationships; membership and inheritance lines are excluded. Room structure instead shows the active room’s members, rules, documents, and exemptions. Knowledge sources shows owned, shared, and subscribed collections and their upkeep. A collection is not a room.

Every relationship type between records declares an effect: it carries context into an answer, states something the answer must say out loud, binds a decision to an obligation, assigns an approver or escalation path, or bounds how long something stays valid. A type whose effect nobody has built yet can never become active, so an edge of that type stays proposed and steers nothing. The graph renders such an edge muted, the same as an edge whose type has no effect at all: colour on an edge means it acts, muted means it does not.

The cockpit summarises the same finding as one number, without the graph view open: the share of active relations whose type has no effect, with the breakdown by effect underneath.

Set Labels directly on the graph to Selected only (default), All, or None. Selected only names the chosen node or the endpoints of a selected relationship, not every neighbor. None hides even selected labels. Full titles remain available in details and hover tooltips. Find nodes opens a collapsible search with keyboard-accessible results only from the current graph view; active type and focus filters still apply. Selection, filters, zoom, and pan preserve the label mode. Another view or room starts with Selected only. The existing Fit selection, Show whole graph, and Back to last focus commands explicitly control framing.

Creating and importing

“New record” (type and title, created as a draft) and “Import” sit in the inventory header and in the rail. The import shows a preview before anything is written. Wikilinks, Markdown links, and “relations” lists inside imported notes become governed associations and appear as lines in the graph right after the import.

Documents

Imported, accepted documents appear as files of their room and as leaves in the graph. Their content and parts are maintained in the import management; the workspace shows them as part of the room’s knowledge.

Cross-room decisions for role holders

Anyone holding a cross-cutting role (Architecture, Security, Business) or the Auditor role sees an additional “Cross-room decisions” folder in the rail, listing the readable decisions of every room. This folder is read-only. Details on the roles: Help: cross-cutting roles and auditor

How answers cite this knowledge

Every answer in the chat carries its verdict first, together with the room, the data class, and the model: “Checked & backed”, “Advisory basis”, “No reliable basis”, or, while the answer is still being generated, “Being checked …”. The raised numbers in the text are buttons: pressing one opens the list of bases and jumps to the source it names. If that source is a decision or a rule, the row leads straight here into the knowledge workspace. If it is a retrieved passage of a document, it opens the run’s evidence bundle instead, because that is the only place where the cited passage is recorded. The heading of the basis list counts cited sources apart from records that were only context for the answer, and a context-only row says so.