naive-framework 0.0.0-stage → 0.2.0

package/docs/ontology.json

@@ -0,0 +1,796 @@
+{
+  "version": "0.5.0",
+  "note": "The system's nouns (EE-014). Standards first: a noun uses an established term with its standard meaning, and is coined only when none exists ('ours'). Retired nouns list what replaced them; schema/check-nouns.mjs fails when one reappears in the checked files. References are ids in <layer>/references/references.json.",
+  "check": [
+    "schema/",
+    "docs/ontology.md",
+    "docs/design/VENTURES_2026-10-27.md",
+    "purpose/frameworks/product-anatomy/",
+    "AGENTS.md",
+    "README.md",
+    "site/content/"
+  ],
+  "nouns": [
+    {
+      "noun": "Everything Ecosystem",
+      "level": "system",
+      "meaning": "The name of the system",
+      "standard": "ours",
+      "status": "kept"
+    },
+    {
+      "noun": "the system",
+      "level": "system",
+      "meaning": "How files refer to the whole. Proposed genus (EE-024): a venture development framework; operating system and operating model are set aside",
+      "standard": "EOS (Wickman) for 'operating system'",
+      "status": "kept"
+    },
+    {
+      "noun": "venture development framework",
+      "level": "system",
+      "meaning": "Proposed genus of the Everything Ecosystem (EE-024): an opinionated framework for developing ventures, in the same genus as web development frameworks. Like them it gives conventions over configuration (one default per choice, with references), a fixed structure the builder fills in (the venture folder, layers and records), generators (init-venture), checks that run like tests, a data model, and packages (packages/<name>/package.json, EE-071). The builder's venture calls on it, and its checks call back on the venture's records",
+      "standard": "software framework (Johnson and Foote 1988; Rails' convention over configuration) applied to venture development (venture building, venture studios)",
+      "status": "new"
+    },
+    {
+      "noun": "method",
+      "level": "system",
+      "meaning": "What to do: Product Anatomy, handoffs; MAD, the method for building software, is a separate product (EE-038)",
+      "standard": "common usage",
+      "status": "kept"
+    },
+    {
+      "noun": "schema",
+      "level": "system",
+      "meaning": "What to record: venture.json, products, decisions, references",
+      "standard": "JSON Schema",
+      "status": "kept"
+    },
+    {
+      "noun": "tooling",
+      "level": "system",
+      "meaning": "What helps do it: scripts, skills, agent rules",
+      "standard": "common usage",
+      "status": "kept"
+    },
+    {
+      "noun": "workspace",
+      "level": "system",
+      "meaning": "One builder's instance of the system, declared by workspace.json",
+      "standard": "common software usage",
+      "status": "kept"
+    },
+    {
+      "noun": "layer",
+      "level": "system",
+      "meaning": "One of the six: purpose, knowledge, operations, evidence, governance, interface (execution folded into operations, EE-038). A layer organizes the framework repository (its manifest is <layer>/layer.json). It is a property of a record type, not a venture folder (EE-071)",
+      "standard": "ours",
+      "status": "kept"
+    },
+    {
+      "noun": "venture",
+      "level": "venture",
+      "meaning": "The unit: anything a builder undertakes, from a hobby to a company. Ventures can hold ventures",
+      "standard": "common business usage",
+      "status": "new"
+    },
+    {
+      "noun": "phase",
+      "level": "venture",
+      "meaning": "How far a venture has come: discovery, validation, beachhead, scale, platform",
+      "standard": "Blank; Moore",
+      "status": "new",
+      "references": [
+        "blank-2005-four-steps",
+        "moore-1991-crossing-the-chasm",
+        "moore-1995-inside-the-tornado"
+      ]
+    },
+    {
+      "noun": "gate",
+      "level": "venture",
+      "meaning": "The test for leaving a phase: problem-solution fit, product-market fit (retention), repeatability, market leadership",
+      "standard": "Andreessen; Zook and Allen",
+      "status": "new",
+      "references": [
+        "andreessen-2007-only-thing-that-matters",
+        "zook-allen-2012-repeatability"
+      ]
+    },
+    {
+      "noun": "ambition",
+      "level": "venture",
+      "meaning": "Why the venture exists and how far it means to go: hobby, survival, lifestyle, managed growth, aggressive growth",
+      "standard": "IRS (hobby); venture-type literature",
+      "status": "new",
+      "references": [
+        "irs-treas-reg-1-183-2",
+        "elgar-what-do-entrepreneurs-create"
+      ]
+    },
+    {
+      "noun": "legal form",
+      "level": "venture",
+      "meaning": "none, sole-prop, partnership, llc, s-corp, c-corp, benefit-corp, nonprofit",
+      "standard": "US entity types",
+      "status": "kept"
+    },
+    {
+      "noun": "funding",
+      "level": "venture",
+      "meaning": "bootstrapped, grant, angel, venture capital, debt, mixed",
+      "standard": "common usage",
+      "status": "new"
+    },
+    {
+      "noun": "industry",
+      "level": "venture",
+      "meaning": "What the venture produces, by its current flagship",
+      "standard": "NAICS",
+      "status": "new",
+      "references": [
+        "naics-2022",
+        "gics-msci"
+      ]
+    },
+    {
+      "noun": "core product",
+      "level": "venture",
+      "meaning": "The promise, who it is made to, what it must not deliver, and the competence behind it",
+      "standard": "Kotler; Prahalad and Hamel",
+      "status": "kept",
+      "references": [
+        "kotler-core-product",
+        "prahalad-hamel-1990-core-competence"
+      ]
+    },
+    {
+      "noun": "client",
+      "level": "venture",
+      "meaning": "Was the record for a party a venture serves; not universal, since many ventures have customers, users, members or an audience instead. Now a value of an account's relationship (served under a professional relationship)",
+      "standard": "common usage",
+      "status": "retired",
+      "replaced_by": "account (relationship: client)",
+      "retired_pattern": "clients/|client\\.json|client\\.schema"
+    },
+    {
+      "noun": "account",
+      "level": "venture",
+      "meaning": "A named party a venture keeps a record for, at accounts/<id>/account.json, with a relationship: client, customer, user, member, partner or other. Optional; who a product serves in general is its market",
+      "standard": "CRM usage (Salesforce, HubSpot: account)",
+      "status": "new"
+    },
+    {
+      "noun": "relationship",
+      "level": "venture",
+      "meaning": "How a party or market stands to the venture: customer (buys), client (served under a professional relationship), user (uses, may not pay), member (belongs), audience (reads, watches or listens; markets only), partner",
+      "standard": "common business usage; client as a customer of professional services",
+      "status": "new"
+    },
+    {
+      "noun": "link",
+      "level": "venture",
+      "meaning": "What crosses from one venture into another, one way, with a border",
+      "standard": "Clark's work/family border theory",
+      "status": "kept"
+    },
+    {
+      "noun": "venture profile",
+      "level": "venture",
+      "meaning": "The readable companion to venture.json: narrative, pillars, changelog",
+      "standard": "ours",
+      "status": "new"
+    },
+    {
+      "noun": "function",
+      "level": "venture",
+      "meaning": "A business function with one accountable owner. One person may own several. A solo founder owns them all. Decision rights and the team plan point at function owners (EE-071). department is the alias for one release",
+      "standard": "business function (common usage)",
+      "status": "new"
+    },
+    {
+      "noun": "pillar",
+      "level": "venture",
+      "meaning": "Product, brand and business, in every venture",
+      "standard": "ours",
+      "status": "kept"
+    },
+    {
+      "noun": "venture template",
+      "level": "venture",
+      "meaning": "The scaffold for a venture: pillars, roles, decision rights",
+      "standard": "ours",
+      "status": "new"
+    },
+    {
+      "noun": "product",
+      "level": "purpose",
+      "meaning": "One thing a venture offers, stored as a card in products/",
+      "standard": "common usage",
+      "status": "kept"
+    },
+    {
+      "noun": "market",
+      "level": "purpose",
+      "meaning": "Who a product serves: customer type, segment, geography, vertical or horizontal",
+      "standard": "Abell (customer groups)",
+      "status": "new",
+      "references": [
+        "abell-1980-defining-the-business"
+      ]
+    },
+    {
+      "noun": "job",
+      "level": "purpose",
+      "meaning": "The need a product meets",
+      "standard": "Abell (customer functions); jobs to be done",
+      "status": "new",
+      "references": [
+        "abell-1980-defining-the-business"
+      ]
+    },
+    {
+      "noun": "technology",
+      "level": "purpose",
+      "meaning": "How a product meets the need",
+      "standard": "Abell (alternative technologies)",
+      "status": "new",
+      "references": [
+        "abell-1980-defining-the-business"
+      ]
+    },
+    {
+      "noun": "offering",
+      "level": "purpose",
+      "meaning": "product, service, platform, content, marketplace",
+      "standard": "common usage",
+      "status": "new"
+    },
+    {
+      "noun": "business model",
+      "level": "purpose",
+      "meaning": "How a product earns, by St. Gallen pattern names",
+      "standard": "St. Gallen Business Model Navigator",
+      "status": "new",
+      "references": [
+        "gassmann-2014-business-model-navigator"
+      ]
+    },
+    {
+      "noun": "portfolio role",
+      "level": "purpose",
+      "meaning": "A product's place in each phase: flagship, substrate, revenue engine, wedge, option, end product",
+      "standard": "portfolio strategy",
+      "status": "new"
+    },
+    {
+      "noun": "wedge",
+      "level": "purpose",
+      "meaning": "A portfolio role: the narrow product or segment used to enter a market",
+      "standard": "Dixon (2010)",
+      "status": "kept",
+      "references": [
+        "dixon-2010-thin-edge-of-the-wedge"
+      ]
+    },
+    {
+      "noun": "Product Anatomy",
+      "level": "purpose",
+      "meaning": "The method that judges products against the core product",
+      "standard": "ours",
+      "status": "kept"
+    },
+    {
+      "noun": "Succession Matrix",
+      "level": "purpose",
+      "meaning": "Part of Product Anatomy that assigns portfolio roles by phase",
+      "standard": "ours",
+      "status": "kept"
+    },
+    {
+      "noun": "decision",
+      "level": "knowledge",
+      "meaning": "A logged choice with an id (EE- or a venture's own prefix)",
+      "standard": "ADR practice",
+      "status": "kept"
+    },
+    {
+      "noun": "reference",
+      "level": "knowledge",
+      "meaning": "A source behind a default, recorded per layer with a stance",
+      "standard": "citation practice",
+      "status": "new"
+    },
+    {
+      "noun": "tier",
+      "level": "operations",
+      "meaning": "One of MAD's four levels: governance, delivery, software engineering, automation; MAD is a separate product, and Mentura records name a tier only where a venture uses MAD (EE-038)",
+      "standard": "architecture tiers",
+      "status": "new"
+    },
+    {
+      "noun": "handoff",
+      "level": "operations",
+      "meaning": "One unit of delegated work: a JSON record (role, decision classes, done-criteria, status, attempts) at <venture>/operations/handoffs/<id>.json with a Markdown brief beside it",
+      "standard": "common operations usage",
+      "status": "kept"
+    },
+    {
+      "noun": "done-criterion",
+      "level": "operations",
+      "meaning": "One check that says a handoff is finished: conformance (a command, no model, no reviewer), self-proof (the change exercised for real, with output) or review (fit to intent, by a named role)",
+      "standard": "definition of done (Scrum)",
+      "status": "new"
+    },
+    {
+      "noun": "eval",
+      "level": "evidence",
+      "meaning": "A test of whether something worked; evals are grouped in eval suites (eval-suite.schema.json)",
+      "standard": "AI evals",
+      "status": "kept"
+    },
+    {
+      "noun": "evidence",
+      "level": "evidence",
+      "meaning": "The recorded result of one run of a check or eval: subject and version, each criterion's outcome and its output, at <venture>/evidence/results/<id>.json. Append-only",
+      "standard": "common audit usage",
+      "status": "new"
+    },
+    {
+      "noun": "role",
+      "level": "governance",
+      "meaning": "A person's or agent's job; never a product's place in the portfolio",
+      "standard": "decision rights (RACI, RAPID)",
+      "status": "kept"
+    },
+    {
+      "noun": "team plan",
+      "level": "governance",
+      "meaning": "Who the venture needs, agent or person, by phase, with the authority each holds and where a human stays in the loop; recruiting briefs for open person roles (operations/team-plan.json, EE-029)",
+      "standard": "workforce planning (common HR usage)",
+      "status": "new"
+    },
+    {
+      "noun": "human loop",
+      "level": "governance",
+      "meaning": "The person who decides, reviews or does the part of a task that agents cannot, may not, or are not known to do; named for every such agent task",
+      "standard": "human-in-the-loop (common AI usage)",
+      "status": "new"
+    },
+    {
+      "noun": "capability register",
+      "level": "evidence",
+      "meaning": "What agents can, cannot, may not or are not yet known to do, task by task, with sources and dates, fed by research and our own evals (evidence/capabilities/agent-capabilities.json, EE-029)",
+      "standard": "ours",
+      "status": "new"
+    },
+    {
+      "noun": "decision right",
+      "level": "governance",
+      "meaning": "Who may decide what, at one of four levels: decide, decide-inform, recommend-approve, escalate. A venture may tighten the template, never loosen it without a named decision",
+      "standard": "decision rights (RAPID, DACI)",
+      "status": "kept"
+    },
+    {
+      "noun": "console",
+      "level": "interface",
+      "meaning": "A custom interface built for the system: a viewer over a venture's records",
+      "standard": "common software usage",
+      "status": "kept"
+    },
+    {
+      "noun": "interface",
+      "level": "interface",
+      "meaning": "A tool through which a person, with agents, works across all or most other layers at once in one session (reaches at least four of the six). A tool that serves one or two layers is an integration of those layers, however good its screen is",
+      "standard": "ours, a narrowed sense of user interface",
+      "status": "new"
+    },
+    {
+      "noun": "agent harness",
+      "level": "interface",
+      "meaning": "An AI harness in which the model directs its own steps and tool use in a loop toward a goal, acting on files, tools and systems between the person's turns, under permissions (Claude Code, Cursor, Codex, Hermes Agent). The default kind of interface. Every agent harness is an AI harness; a chatbot is not an agent harness",
+      "standard": "agent harness (industry usage)",
+      "status": "new",
+      "references": [
+        "anthropic-2024-building-effective-agents"
+      ]
+    },
+    {
+      "noun": "AI harness",
+      "level": "interface",
+      "meaning": "A product that is the software around a model: the person's work happens in exchanges with it, so without the model nothing is left. A chatbot is one. The model answers; the person acts",
+      "standard": "harness (industry usage)",
+      "references": [
+        "anthropic-2024-building-effective-agents"
+      ],
+      "status": "new"
+    },
+    {
+      "noun": "AI feature",
+      "level": "interface",
+      "meaning": "A model used inside a product that does its job without it (summaries, search, drafting). Test: remove the model and the product still works. Most apps that implement AI are here, not harnesses",
+      "standard": "common product usage",
+      "references": [
+        "anthropic-2024-building-effective-agents"
+      ],
+      "status": "new"
+    },
+    {
+      "noun": "custom interface",
+      "level": "interface",
+      "meaning": "An interface built for the system or a venture rather than bought, such as the operator console",
+      "standard": "common software usage",
+      "status": "new"
+    },
+    {
+      "noun": "integration",
+      "level": "system",
+      "meaning": "A tool or service one layer uses, listed in <layer>/tooling/integrations.json (Obsidian for knowledge, Linear for operations, GitHub checks for evidence). An interface reaches integrations; it is not one",
+      "standard": "systems integration",
+      "status": "kept"
+    },
+    {
+      "noun": "kit",
+      "level": "venture",
+      "meaning": "Mentura's word (EE-071): an enhanced package that adds automations, agent workflows, richer skills and connectors, at platform/kits/<name>/kit.json. A kit names the one package it extends and never replaces it, so the package works without the kit. The framework does not use kit for its own manifests (was the layer bundle at <layer>/kit.json)",
+      "standard": "product bundling (Adams and Yellen 1976), kept for the platform",
+      "status": "kept"
+    },
+    {
+      "noun": "sphere",
+      "level": "venture",
+      "meaning": "Old name for the unit",
+      "standard": "none",
+      "status": "retired",
+      "replaced_by": "venture",
+      "retired_pattern": "\\bspheres?\\b"
+    },
+    {
+      "noun": "stage",
+      "level": "venture",
+      "meaning": "Old formation stage (hobby, venture, company)",
+      "standard": "none",
+      "status": "retired",
+      "replaced_by": "phase, legal form and ambition",
+      "retired_pattern": "\"stage\"\\s*:"
+    },
+    {
+      "noun": "kind",
+      "level": "venture",
+      "meaning": "Old sphere kinds (venture, client)",
+      "standard": "none",
+      "status": "retired",
+      "replaced_by": "venture, with accounts as records",
+      "retired_pattern": "\"kind\"\\s*:\\s*\"(venture|client)\""
+    },
+    {
+      "noun": "Wedge (phase)",
+      "level": "venture",
+      "meaning": "Old first market phase",
+      "standard": "none",
+      "status": "retired",
+      "replaced_by": "validation (wedge stays a portfolio role)",
+      "retired_pattern": "\"id\"\\s*:\\s*\"wedge\""
+    },
+    {
+      "noun": "Core Engine",
+      "level": "venture",
+      "meaning": "Old scale phase",
+      "standard": "none",
+      "status": "retired",
+      "replaced_by": "scale",
+      "retired_pattern": "Core Engine|core-engine"
+    },
+    {
+      "noun": "Horizon (phase)",
+      "level": "venture",
+      "meaning": "Old last phase",
+      "standard": "none",
+      "status": "retired",
+      "replaced_by": "platform (Three Horizons stays a lens)",
+      "retired_pattern": "\"id\"\\s*:\\s*\"horizon\""
+    },
+    {
+      "noun": "entity profile",
+      "level": "venture",
+      "meaning": "The old name for the venture profile",
+      "standard": "none",
+      "status": "retired",
+      "replaced_by": "venture profile",
+      "retired_pattern": "entity profile"
+    },
+    {
+      "noun": "company template",
+      "level": "venture",
+      "meaning": "Old name of the venture template",
+      "standard": "none",
+      "status": "retired",
+      "replaced_by": "venture template",
+      "retired_pattern": "company[- ]template"
+    },
+    {
+      "noun": "orientation",
+      "level": "venture",
+      "meaning": "Proposed for-profit/nonprofit axis, dropped before use",
+      "standard": "none",
+      "status": "retired",
+      "replaced_by": "legal form",
+      "retired_pattern": "\"orientation\"\\s*:"
+    },
+    {
+      "noun": "data model",
+      "level": "system",
+      "meaning": "The list of every record type in the ecosystem, the layer that owns it, its schema, where its records live and what it references (schema/data-model.json). It is the master map; no single schema contains everything",
+      "standard": "data model (ANSI/SPARC; entity-relationship modelling, Chen 1976)",
+      "status": "new"
+    },
+    {
+      "noun": "record type",
+      "level": "system",
+      "meaning": "One kind of record in the data model, such as venture, product, handoff or evidence, owned by exactly one layer or by the system",
+      "standard": "record type (database usage)",
+      "status": "new"
+    },
+    {
+      "noun": "layer manifest",
+      "level": "system",
+      "meaning": "The file (<layer>/layer.json, system layer at schema/layer.json) that lists what one layer of the framework repository holds: its skills, the record types it still owns, those it reads and writes, and its checks. Layer relationships are derived from manifests (EE-018, EE-071)",
+      "standard": "package manifest (common software usage)",
+      "status": "new"
+    },
+    {
+      "noun": "vault",
+      "level": "system",
+      "meaning": "The folder of documents (Markdown notes and JSON records) that holds a workspace's venture folders, their records and decisions. Every workspace has one; a venture outside software may need nothing else",
+      "standard": "Obsidian's name for a folder of notes; generically a knowledge base",
+      "status": "new"
+    },
+    {
+      "noun": "repository (repo)",
+      "level": "system",
+      "meaning": "A version-controlled store, normally Git, holding code and the documents that ship with it (docs-as-code). A venture that builds software needs at least one; repo is the short form",
+      "standard": "version control (Git: repository)",
+      "status": "new"
+    },
+    {
+      "noun": "cap table",
+      "level": "governance",
+      "meaning": "The record of who owns the venture and on what terms: share classes, holders, grants with vesting, the option pool, SAFEs and notes (governance/ownership.json)",
+      "standard": "capitalization table (common startup and finance usage)",
+      "status": "new"
+    },
+    {
+      "noun": "share class",
+      "level": "governance",
+      "meaning": "A kind of share (or LLC unit) with its own votes, price and rights: common, preferred, super-voting, non-voting",
+      "standard": "corporate law (classes of stock)",
+      "status": "new"
+    },
+    {
+      "noun": "vesting",
+      "level": "governance",
+      "meaning": "Earning granted shares over time, commonly four years with a one-year cliff, so that someone who leaves early keeps only what they earned",
+      "standard": "common startup usage",
+      "status": "new"
+    },
+    {
+      "noun": "founder agreement",
+      "level": "governance",
+      "meaning": "What founders agreed with each other: roles, commitment, IP assignment, departure and deadlock terms; required once two or more founders share ownership",
+      "standard": "common startup usage",
+      "status": "new"
+    },
+    {
+      "noun": "board",
+      "level": "governance",
+      "meaning": "A formal board of directors (or managers, or trustees), which holds legal authority, or an advisory board, which advises and decides nothing (governance/board.json)",
+      "standard": "corporate law; Feld and Ramsinghani, Startup Boards",
+      "status": "new"
+    },
+    {
+      "noun": "reserved matter",
+      "level": "governance",
+      "meaning": "A decision only the formal board may make, such as issuing shares or selling the company",
+      "standard": "corporate governance usage",
+      "status": "new"
+    },
+    {
+      "noun": "investor right",
+      "level": "governance",
+      "meaning": "A right an investor gets with a class or instrument: board seat, information, pro-rata, protective provisions, anti-dilution, drag-along, tag-along, right of first refusal and others",
+      "standard": "NVCA model legal documents",
+      "status": "new"
+    },
+    {
+      "noun": "liquidation waterfall",
+      "level": "governance",
+      "meaning": "The order and amounts in which sale proceeds reach each owner. Retired here because waterfall is a delivery methodology in MAD's delivery tier",
+      "standard": "venture finance usage",
+      "status": "retired",
+      "replaced_by": "preference stack",
+      "retired_pattern": "liquidation waterfall|waterfall\\.mjs"
+    },
+    {
+      "noun": "exit",
+      "level": "governance",
+      "meaning": "How owners realize value or the venture ends: acquisition, IPO, secondary sale, merger, management buyout, wind-down, or hold (governance/exit.json)",
+      "standard": "venture finance usage",
+      "status": "new"
+    },
+    {
+      "noun": "preference stack",
+      "level": "governance",
+      "meaning": "The order and amounts in which a sale's proceeds reach each owner, preferences first by seniority, then common; computed from the cap table by schema/payouts.mjs, never typed",
+      "standard": "venture finance usage (pref stack; Feld and Mendelson, Venture Deals)",
+      "status": "new"
+    },
+    {
+      "noun": "publication policy",
+      "level": "governance",
+      "meaning": "Where a venture publishes and who may publish what there: its channels, the guidelines each follows, the checks and preview every publication passes, and who drafts and approves by role or team (governance/publication-policy.json, EE-025)",
+      "standard": "content governance; communications or disclosure policy (corporate usage)",
+      "status": "new"
+    },
+    {
+      "noun": "channel",
+      "level": "governance",
+      "meaning": "A place the venture publishes to (website, docs site, social account, newsletter, app store, press, investor update, regulatory filing); its destination decides which guidelines apply",
+      "standard": "marketing channel (Kotler, Marketing Management)",
+      "status": "new"
+    },
+    {
+      "noun": "publication",
+      "level": "governance",
+      "meaning": "One act of making something public on a channel; always a handoff under the public-commitment decision class, previewed, checked and approved by a person",
+      "standard": "common usage",
+      "status": "new"
+    },
+    {
+      "noun": "brand guidelines",
+      "level": "governance",
+      "meaning": "The rules for using the venture's visual and verbal identity, kept by the brand pillar",
+      "standard": "brand guidelines or brand book (common marketing usage)",
+      "status": "new"
+    },
+    {
+      "noun": "editorial guidelines",
+      "level": "governance",
+      "meaning": "What content covers and how it is written, separate from brand voice; a style guide is one part",
+      "standard": "editorial guidelines and style guide (publishing usage)",
+      "status": "new"
+    },
+    {
+      "noun": "telos",
+      "level": "purpose",
+      "meaning": "The end a venture exists to reach (purpose/telos.json): statement, end state, measures, the owners' intended outcome, and exit criteria for each phase. Start with the end: other layers derive from it",
+      "standard": "Aristotle (final cause); Covey, begin with the end in mind",
+      "status": "new"
+    },
+    {
+      "noun": "exit criterion",
+      "level": "purpose",
+      "meaning": "What must be true for a venture to leave a phase, written in its telos and tied to a telos measure; it refines that phase's generic gate. Not an owner's exit (governance)",
+      "standard": "Stage-Gate exit criteria (Cooper)",
+      "status": "new"
+    },
+    {
+      "noun": "template",
+      "level": "system",
+      "meaning": "A fill-in starting point for one record or document: the fields, what to write in each and what a strong one looks like. A kit holds templates; a template holds no rules and checks nothing",
+      "standard": "common usage (document template)",
+      "status": "new"
+    },
+    {
+      "noun": "validation score",
+      "level": "purpose",
+      "meaning": "The probability that a venture is validated: a weighted average of sub-scores (problem, solution, product-market fit, pricing, go-to-market, team, operations readiness), each a Jev probability times its evidence weight, with floors; replaces a declared phase gate (EE-026)",
+      "standard": "ours, after Blank's customer validation",
+      "references": [
+        "blank-2005-four-steps"
+      ],
+      "status": "new"
+    },
+    {
+      "noun": "evidence grade",
+      "level": "purpose",
+      "meaning": "How much a validation record's cited evidence can be trusted: high, moderate, low or very low, from the kind of signal, the audience, the sample, the specificity and the age; a claim with no evidence is very low",
+      "standard": "GRADE certainty of evidence",
+      "references": [
+        "grade-handbook",
+        "fitzpatrick-2013-mom-test"
+      ],
+      "status": "new"
+    },
+    {
+      "noun": "need-now score",
+      "level": "purpose",
+      "meaning": "The probability that a venture needs a record type in its current phase and the next, from priors raised or lowered by facts about the venture; records below 0.5 are held back unless the builder asks, so builders don't overbuild (EE-028)",
+      "standard": "ours; just-in-time (lean manufacturing) and YAGNI (extreme programming) in spirit",
+      "status": "new"
+    },
+    {
+      "noun": "derived answer",
+      "level": "operations",
+      "meaning": "A MAD answer taken from a venture's records (telos, ownership, board, form, decision rights) instead of asked again; it names the record it came from Retired with MAD's move out of Mentura (EE-038).",
+      "standard": "ours",
+      "status": "retired"
+    },
+    {
+      "noun": "route",
+      "level": "interface",
+      "meaning": "The address of one record type or command in a venture, such as purpose/validation/problem: a layer, then a kit when the record sits in a nested kit, then the record. Generated from the data model and kits; the CLI, the MCP server and the HTTP API share one route table (EE-030)",
+      "standard": "routing in web frameworks (Next.js App Router, Rails routes)",
+      "status": "new"
+    },
+    {
+      "noun": "draft",
+      "level": "interface",
+      "meaning": "A gated record an agent wrote, held in <venture>/_drafts/ until a person accepts it; the decision class of the record says it is a person's to make (EE-030)",
+      "standard": "common usage (draft for approval)",
+      "status": "new"
+    },
+    {
+      "noun": "provenance",
+      "level": "system",
+      "meaning": "Who or what produced a record, by which activity, from what, and under which decision: explicit in the provenance log for writes through the router, implicit in git history for everything else (EE-031)",
+      "standard": "W3C PROV (PROV-DM: entity, activity, agent)",
+      "status": "new"
+    },
+    {
+      "noun": "provenance log",
+      "level": "system",
+      "meaning": "A venture's append-only record of writes, <venture>/provenance.jsonl: one line per write naming the file, the activity (write, draft, accept, baseline), the person or agent and the interface, what it was derived from and the decision; each line carries the previous line's hash (EE-031)",
+      "standard": "W3C PROV; hash-chained append-only log (common audit usage)",
+      "status": "new"
+    },
+    {
+      "noun": "layout",
+      "level": "interface",
+      "meaning": "The context that wraps a route: the system, layer and kit purpose, skills and references, the template, the gate and what need-now says, given to an agent before it acts on the route (EE-032)",
+      "standard": "Next.js App Router (layout)",
+      "status": "new"
+    },
+    {
+      "noun": "view",
+      "level": "interface",
+      "meaning": "A route rendered as a page for a person; the Markdown form of a record or command result. The operator console will render views (EE-032)",
+      "standard": "Next.js App Router (page); MVC view",
+      "status": "new"
+    },
+    {
+      "noun": "route group",
+      "level": "interface",
+      "meaning": "A named set of routes that shares a layout without changing their paths; one per phase, (discovery) to (platform), holding the routes need-now suggests in that phase (EE-032)",
+      "standard": "Next.js App Router (route groups)",
+      "status": "new"
+    },
+    {
+      "noun": "slot",
+      "level": "interface",
+      "meaning": "One part of a page that renders on its own beside others, such as @validation in the venture overview; a slot that fails shows its error while the rest render (EE-032)",
+      "standard": "Next.js App Router (parallel routes, @slot)",
+      "status": "new"
+    },
+    {
+      "noun": "route alias",
+      "level": "interface",
+      "meaning": "An old route kept after a rename, which the router follows to the new one with a deprecation note (EE-032)",
+      "standard": "common API usage (deprecation, redirects)",
+      "status": "new"
+    },
+    {
+      "noun": "strategic foundation",
+      "level": "venture",
+      "meaning": "The records a founder keeps in front of them every day until they are muscle memory, answering why, what, who, how, when, where and whether, with brand beside them (purpose/strategic-foundation.json). Each foundation statement is an attribute of an existing record; changing one is deliberate (type to confirm) and confirmed statements unlock delegation (EE-051, EE-052)",
+      "standard": "strategic foundation in strategic planning (mission, vision, values), widened by the Five Ws and How",
+      "status": "new"
+    },
+    {
+      "noun": "guiding statement",
+      "level": "venture",
+      "meaning": "Retired for strategic foundation and foundation statement (EE-052)",
+      "standard": "ours",
+      "status": "retired"
+    }
+  ]
+}