pitch.headless.legal

headless.legal

The headless, agent-first legal stack — documented.

Nothing is sold here. The canon is keyless, free, and reads itself to your agent — markdown at heart, designed pages on top.

↓ scroll · arrow keys

The last stack still built for humans at screens

Every function of a software business went headless — payments, comms, auth, infra: objects with lifecycles, events with signatures, dashboards demoted to read-models. The legal stack did not. It is still a shelf of per-seat dashboards — practice management, docketing, billing, conflicts, intake, contract lifecycle, e-filing, research, discovery, entity compliance — each one a proprietary screen over records it does not let a machine read.

The thesis this canon publishes: that shelf is, structurally, a small set of resources and typed events over three objects — the Matter (the terminating unit of work), the Asset (the perpetual noun with the docket), and the Journal (the append-only truth from which every state derives). The incumbent categories are views. Views get rebuilt; the party that publishes the vocabulary and the event dictionary is the one everybody rebuilds against.

That is a doctrine under construction, stated in the indicative because the canon argues it — not because the software behind every category ships today. Where this deck asserts a live fact, the fact carries its own state and evidence; everything else is the thesis, labeled as such.

What serves today — and how it serves

headless.legal is the domain-honest home of the Callable Law canon: the flagship essays, the ratified glossary, the Reserved-Act Atlas, and the /can/ answer grid — the vocabulary layer the legal estate's products are built against. Each liveness fact below carries its own evidence, and the one machine artifact the canon has not yet published under its own name is worn amber:

Postedheadless.legal

headless.legal serves — and serves in kind: a request without an HTML Accept header receives the page's markdown source verbatim (content-type: text/markdown). The site practices the agent-first thesis it publishes.

Pendinggate: the canon's own llms.txt published at headless.legal

The machine front door today is the apex itself — a non-HTML request receives the canon's markdown index directly. A dedicated llms.txt carrying the canon's own index is not yet published at this domain, and this deck does not post it green until it is.

Postedheadless.legal/catalog.json

catalog.json serves — the estate's typed capability catalog, machine-readable and keyless: the same catalog the canon's /can/ grid is rendered from.

Postedheadless.legal/glossary

The ratified glossary serves — the terms are addressable, not folklore.

Postedheadless.legal/can

The /can/ answer grid serves — the lawful-scope questions, answered page by page.

The live surface wears a Preview build badge and a standing footer line — nothing here is a live-service claim, and nothing here is legal advice — and this deck repeats both on purpose. Serving is a liveness fact, not a claim about readership or adoption.

canon reachPendinggate: first ninety days of measured canon traffic

▮▮▮posts when first ninety days of measured canon traffic resolves — readership is measured, then published, never asserted in advance. No traffic or citation figure appears anywhere in this deck.

The headless family's bridge into legal

The doctrine has a flagship. headless.ly is the family's product venue — filed as venue.products in the estate's role register — where business software is rebuilt as typed, event-driven APIs designed for agents, not human operators: the composable systems a business-as-code definition materializes into.

Postedheadless.ly

headless.ly serves: the family flagship's front door, carrying the doctrine this brand applies to legal.

headless.legal is the family's bridge into the one vertical where that migration meets a statutory floor. Business software goes headless all the way down; legal goes headless until the law names a person — and that difference is exactly what makes the vertical worth its own canon. The bridge brand documents both halves honestly: everything unreserved becoming resources and events, and the reserved remainder staying human by statute, typed rather than fogged.

3

the canon — headless.legal

vocabulary · glossary · Reserved-Act Atlas · /can/ grid

keyless and free — nothing sold, by design

2

the rails — the legal cell

api.lawyer (demand) · gigs.lawyer (supply) · patent.click (mint)

the estate’s legal economics live here, not at the canon

1

the doctrine — the headless family

headless.ly — venue.products

software built for agents, not humans

The doctrine, applied — and honestly gated

The canon's central technical claim: the incumbent legal-software categories die as UIs and are reborn as resource-and-event slices on the three-object spine — docketing as the Asset's deadline ladder, billing as typed money-states, conflicts as a practitioner-owned protocol instead of a firm-owned database, intake as an event subscription. The category-killer move is publishing the event dictionarymatter.*, deadline.*, meter.*, conflict.* — as a versioned public standard, the way payments published charge.succeeded.

Pendinggate: first versioned event-dictionary release published at headless.legal

The event dictionary is a design target, not a shipped standard. The canon argues for it today; the versioned release posts here when it exists, and no adoption is implied before then.

Pendinggate: counsel-settled reserved-act taxonomy at the cell (patent corridor first)

The Reserved-Act Atlas documents a boundary whose shipped taxonomy is set with licensed counsel at the cell, jurisdiction by jurisdiction — the atlas is the map of that work, not a substitute for it.

Where the reading room exits — the reserved boundary, on rails

The canon's exits are the estate's own rails, and each one's liveness is posted separately:

entityhttps://schema.org.ai/Organization/legal-cell — designed, not formed (gate below)
demand railapi.lawyer — reserved legal acts, callable; A2H2A fulfilment
supply doorgigs.lawyer — licensed humans supplying the reserved acts
motioncanon (B2A, this brand) → rail (B2A2B) → licensed human (A2H2A)
Postedapi.lawyer

api.lawyer serves: the cell's demand rail, where a canon reader's agent becomes a caller.

Postedgigs.lawyer

gigs.lawyer serves: the cell's supply door, where the licensed humans the statute names are recruited.

Postedpatent.click

patent.click serves: the cell's first demand mint, in the corridor where federal authorization settles the practice question.

Pendinggate: entity formation and licensure of the legal cell

The cell's operating entity is designed, not formed. Nothing at this brand waits on that gate — the canon sells nothing — but every transaction the canon routes toward does, and this deck says so rather than borrowing the rails' future tense.

The economics, candidly: this brand has none — that is the design

Nothing is sold at headless.legal. No key, no tier, no sponsorship, no paywall — and no figure of any kind appears in this record. The canon is the estate's owned channel into the legal vertical: it mints qualified demand by being the source agents cite, and the demand lands on api.lawyer, where the cell's posted-rate economics live.

One motion, on purpose: the reader is a machine

B2Athe canon serves the agent directly — keyless markdown negotiation at the apex, catalog.json (llms.txt pending)primary
B2Dthe developer reads the catalog like API docs — key funnel on the rail
A2Aagent to agent — pure machine commerce
B2A2Ba business system calls the rail on its own behalf
B2A2Dour agent serves the deputized developer
B2A2Cour agent serves the consumer
B2H2Aa statute names a human — the licensed supplier in the path
A2H2Athe human is a required supplier: the regulated-cell shape

Every api.* rail in the estate treats being discoverable and callable by agents as the distribution channel. The canon runs the same doctrine one layer up: being readable and citable by agents is the channel. That is why the markdown negotiation and catalog.json are posted liveness facts above rather than roadmap — and why the canon's own llms.txt is worn openly as a pending gate rather than borrowed: the machine surface is the product surface, so it is claimed exactly as it serves.

Pendinggate: resolution of the canon in the agent-discovery layer

Resolution as the citable source for the agent-first legal vocabulary in the agent-discovery index is a design target, not an observed state — no citation or ranking fact is asserted anywhere in this deck.

The ask

The front door is headless.legal — it serves today.

If this was forwarded to you: headless.legal is the free, keyless documentation home of the agent-first legal stack — the essays, glossary, and reserved-act atlas behind the legal estate's products, published so agents can read them directly. Nothing is sold there; every liveness claim in this deck carries its own evidence URL, and every unshipped ambition is labeled pending. If you build agents whose work turns legal: read it. If you know who does: forward this.