Most intranets are filing cabinets. Most ERPs are forms and tables. FIN's intranet is something new: a single living document layer that the humans of a produce business and the agents working alongside them can both read, reason over, and cite.
Walk into any 80-year-old produce distributor and ask the simple question — how do we handle a load of California blackberries that arrived at 38°F instead of 32°F? — and the answer lives in five places at once. It's in a printed SOP nobody updated since 2018. It's in the head of a foreman who's been doing it for thirty years. It's in a Teams chat from last Tuesday. It's in the ERP under a screen no one navigates to anymore. And it's in a PDF user guide on a shared drive.
The information exists. It just can't be retrieved by a system, or cited by a person, or used by the AI agent the company is paying $50,000 a year to consult. The knowledge isn't dead. It's buried.
FIN's intranet has two parts. The first is FIN Central — the universal knowledge layer that holds the produce industry's accumulated truth. Commodity profiles for 487 produce items. Variety details. Vendor histories. Regional patterns. Seasonal windows. FSMA compliance rules. The kind of knowledge that's true whether you're Nathel in Hunts Point or a future distributor in Salinas.
The second is the tenant intranet — for Nathel, this is
nathel-intranet, a private repository that holds what's true today, in this
warehouse, for this company. Today's arrivals. This load's QC outcome. That
customer's order pattern. The morning pricing read from the GM. The PDF invoice
that landed at arrivals@fintail.net at 6:14 AM.
The two layers fuse. When an agent looks up blackberry for Nathel, it doesn't just get the universal commodity profile, and it doesn't just get Nathel's last week of blackberry arrivals. It gets one document that contains both — the world's knowledge of blackberry composed with Nathel's lived operational reality on top.
The metaphor is a taproot — a single root that goes down through three layers, with the deepest layer drawing water from the others. Knowledge moves down the taproot; nothing moves back up. Each layer is owned by exactly one writer.
Animated dashes show the flow. Central writes once. The mirror copies. The tenant composes. No layer writes upward.
Universal produce knowledge must be the same for everyone. FDA / FSMA contract says the commodity profile FIN cites for blackberry can't be different at Nathel than at any future tenant. Centralization protects this.
Every Central update becomes a git commit on the tenant's repo. The full sync history is a queryable timeline. If Central changes a commodity's defect class taxonomy, every tenant's mirror commit records the moment they received it.
Nathel's vendor relationships, customer prices, cost basis, and operational intel never leave Nathel's database. The tenant composes Central knowledge with its own data — but writes only to its own paths.
Collapse any two rungs and you lose one of the three contracts. The system is minimal but not less. Three rungs is the smallest number that preserves universality + sovereignty + auditability at the same time.
Every document in the FIN intranet is a markdown file — the same kind of file you'd write a README in. A human can open it in any text editor. The agent reads the same bytes. The format is deliberately humble: YAML frontmatter on top, body below. The cleverness is in what's in the frontmatter.
Below: a real Central commodity profile, shown two ways. Click the toggle.
--- schema_version: 1 doc_id: commodity_profile_blackberry doc_kind: entity_profile title: Blackberry — Commodity Profile slug: commodity-profile-blackberry data_plane: universal_intelligence visibility: public_anonymized linked_entities: - { type: variety, slug: navaho } - { type: variety, slug: triple_crown } - { type: region, slug: oregon } - { type: region, slug: mexico_central } tags: [commodity, berries, soft_fruit, plane_3] --- # Blackberry — Commodity Profile Blackberries are a perishable soft-fruit commodity with high market sensitivity. They are typically packed in 6-oz, 12-oz, and 18-oz clamshells. Color is matte black; gloss indicates over-ripeness. ## Post-harvest physiology Optimal storage: 32–34°F (0–1°C) at 90–95% relative humidity. Shelf life: 3–6 days under optimal conditions; reduced to 24–48 hours when temperature has been violated by ≥4°F at any point in the chain. ## Common defects - Leaky berries: cell-wall breakdown, typically caused by rough handling or post-harvest temperature shock. - Mold (Botrytis cinerea): gray fuzzy growth at calyx, indicates extended storage above 38°F or condensation in clamshell. - Reversion (red drupelets): a few drupes turn red under light stress; cosmetic, not a quality failure unless > 15% per clamshell. ## Varieties of note The [[variety:navaho]] cultivar is thornless, firm, dominant in Oregon production. [[variety:triple_crown]] is more delicate but flavor-superior; primarily mid-Atlantic. # ...sections continue: Growing regions, Seasonal windows, FSMA notes, # Vendor history, Cited recalls, Linked operational signals
Four frontmatter fields carry most of the system's intelligence:
--- doc_id: nathel_daily_sales_2026_05_18 doc_kind: event_digest data_plane: relationship_data visibility: company source_attribution: - producer: daily_sales_situation - source_events: - evt_5ab9c4 - evt_5abd02 - evt_5acd1f linked_entities: - { type: commodity, slug: blackberry } - { type: vendor, slug: malena_produce } - { type: customer, slug: whole_foods_ne } --- # Daily Sales Situation — May 18, 2026 ## Yesterday's snapshot 312 cases of blackberry sold across 8 customers. Average fill rate: 94% (up 3pp from prior week). ## Attention list - Whole Foods NE: typical Tuesday order missing. Last week ordered 52 cases. Suggested: call the buyer. - Restaurant Depot: 18-case rejection on lot 548591 (calyx mold). Linked to QC inspection.
An agent asks: "Tell me about blackberry." The answer depends on which lens the system serves. Use the tabs below to see all three.
The universal knowledge layer. The same answer everyone gets, today and a year from now. Cited, deterministic, public.
Operational reality. Today's lots, vendor relationships, cost basis, customer patterns. Never leaves Nathel's database.
When the agent asks about blackberry while serving Nathel, both layers are composed into a single document. Universal knowledge on top, operational overlay beneath, all wikilinks resolved.
Each person in a produce business asks different questions. Each gets the same kind of answer: a cited document, the agent can drill into, that links to live operational truth.
The agent answers with the photo, the inspector's narrative, what defect class it falls under, and what the universal commodity profile says about it.
Hunts Point pricing, the GM's Sunday Night Update, in-flight POs, Central's regional pattern for May — all composed into one brief. Cited.
The customer × commodity matrix surfaces the missing order. The agent suggests the outreach. The relevant context — recent pricing, available lots — is attached.
QC history per vendor per commodity, the universal defect taxonomy, the photo evidence chain — all composed into a structured assessment.
A deterministic recall-trace document. Every claim cites an event. Re-renderable six months later with byte-identical output. FSMA 204 ready.
Every document has frontmatter declaring its claims' provenance. The agent doesn't hallucinate — it can show its work, back to the event.
Most enterprise software was built on the assumption that the user is human and the data is private. The interface was the form. The interface was the report. The data sat in tables only the application knew how to reach.
FIN flips that assumption. The data is a document. The interface is the document. The agent reads the same document the human reads. And the document itself carries enough metadata — provenance, links, audience, plane — that the agent doesn't need a separate API to understand it. The document is the API.
This isn't documentation about the system. This is the system.
Not a documentation site about the system — the actual artifact the system reasons over. Every event, every projection, every signal lands as a markdown row the agent can cite.
The same agent question composes industry-wide produce knowledge with this tenant's private operational reality. The fusion happens at the document layer, not at the API boundary.
Every claim carries its event sources in the frontmatter. Re-rendering a recall trace six months later produces byte-identical output. The audit binder is the same artifact the inspector reads on Tuesday.
A produce distributor running on Produce Pro can become a FIN tenant in weeks. The same shape works for Famous Software, Sage X3, NetSuite. The ERP becomes an adapter pack — not a rewrite.
The warehouse worker on a phone, the AI agent in a server room, the federal investigator on a laptop — all reading the same documents. No separate "AI tier" that diverges from what the humans see.
This is the design principle. Everything in FIN's intranet follows from it.
_taproot_mirror/ on the tenant. Rung 3
(tenant) only writes to tenant paths. No layer writes upward. The
data_plane field in every document's frontmatter enforces this at the
security boundary. The tenant's customer prices, cost basis, and vendor
relationships are structurally incapable of reaching Central.
central_pending flag and the tenant overlay carries the full content
until Central catches up. The system gracefully degrades; it never blocks.