Machine interface

Agent access

The same corpus people read is served as structured data. No scraping, no HTML parsing, no authentication — an agent can route on the index and fetch only the documents it needs.

Endpoints

  • GET/llms.txttext/plain

    A plain-text index of the whole corpus, grouped by section, with status and path per document. The cheapest way for an agent to learn what exists before fetching anything.

  • GET/api/kbapplication/json

    Corpus summary: totals, status counts, section inventory, and the document list. Filter with ?section=, ?status=, or ?q=.

  • GET/api/kb/doc/{slug}application/json

    One document: metadata plus the full markdown body, frontmatter stripped. This is the read primitive.

Routing rule

Load the smallest thing that answers the question. The corpus is 1,594 documents and 20 MB — reading all of it is never the right move.

  1. 01Fetch /llms.txt once. It is the map: section, status, path, size.
  2. 02Pick the section that owns the question. Canon and Architecture answer "what is true"; Business and Strategy answer "why".
  3. 03Fetch only the documents you need through /api/kb/doc/{slug}.
  4. 04Prefer canon status. If a document is superseded, find what replaced it before citing it.
  5. 05If a document is unclassified, treat it as a claim, not as authority.

Section map

32 sections
business/295
architecture/282
strategy/197
internal/126
operations/108
developers/104
documentation/102
platform/80
canonical/58
connectors/45
development/22
product/22
docs/21
triage/14
public/13
getting-started/9
resources/9
the-solution/9
implementation/8
solutions/8
the-problem/8
integrations/7
agents/6
how-it-works/6
security-and-governance/5
ai/4
reference/4
spine/4
spineworkspace/4
company/3
closure/2
work/2

Example

# 1. what exists
curl -s /llms.txt | head -40

# 2. what is authoritative
curl -s '/api/kb?status=canon' | jq '.docs[] | {title, slug}'

# 3. read one document
curl -s '/api/kb/doc/canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON' \
  | jq -r '.content' | head -60

Write boundary

Triage only

The read surface above is open. Writes are not: the triage agent may stage a candidate and nothing more. Only the governed promotion path can publish organizational memory, and high confidence does not itself authorize promotion.

Triage may write
  • triage item
  • extracted candidate
  • classification
  • entity links
  • provenance
  • confidence dimensions
  • conflict findings
  • proposed memory scope
  • governance recommendation
  • review state
Triage may never write
  • canonical entity state
  • approved organizational memory
  • authoritative policy
  • permissions
  • authority grants
  • canonical relationships
  • promoted outcomes