Eve library

Delivery and release · chapter 2 · evidence · 7 October 2026

Evidence

Revision 3

On this page

Pinned excerpts and command output behind the chapter's slides (guide release-acceptance) and its brief (Eve document a0654781-b80b-4b26-b1b5-d2645a6b5fee). Every excerpt is the repository at commit b6f1ccf1c111a1b364faa114524aad0181975ed5, copied by the command shown above it. No release was accepted or gated. One thing was run: the member web application, to see what a deferred room answers. It is at the end.

Values read from the code and pages#

Produced by check-data.py in docs/audits/presentation-center-eve-redesign-release-acceptance/2026-10-07/, which reads each value from the pinned source and compares it with the words on the slides. All twelve comparisons were equal. The values it read:

json
{
 "scopedRooms": [
  "tara",
  "nyx",
  "arete",
  "nisaba"
 ],
 "deferredRooms": [
  "veritas",
  "metis"
 ],
 "currentRelease": "V1.0",
 "nativeRelease": "V1.1",
 "deferredRelease": "V1.2",
 "deferredReason": "domain_deferred_to_v1_2",
 "noticeCarriesTheReason": true,
 "releaseTable": [
  [
   "V1.0",
   "Web + PWA. Four rooms: Tara, Nyx, Arete, Nisaba. Crypto payments only."
  ],
  [
   "V1.1",
   "Native iOS/Android apps, the watch companions, and the fiat rails."
  ],
  [
   "V1.2",
   "Restores the Veritas and Metis rooms."
  ]
 ],
 "brandSaysDeferralIsAboutShowing": true,
 "brandSaysOperatorPathsExempt": true,
 "brandSaysOneEdit": true,
 "brandSaysEveNeverShownToMembers": true,
 "statusWords": [
  "Shipped / wired",
  "Built but unwired",
  "Gated",
  "Proposed / backlog"
 ],
 "charterClaimsNoDelivery": true,
 "charterNoClosure": true,
 "glossaryNames": {
  "Sophia": true,
  "Iris": true,
  "Psyche": true,
  "Isis": true,
  "Yemaya": true,
  "Aje": true,
  "Themis": true
 },
 "themisLine": "Academic-integrity adjudication referenced by Metis assessments and tutoring (`libs/themis`).",
 "yemayaLine": "Rendering substrate for media surfaces consumed by Metis and other domains (`libs/yemaya`).",
 "promiseIsADegradationContract": true,
 "sharedSlides": {
  "three-release-contract": [
   "timeline",
   "eve"
  ],
  "how-to-read-evidence": [
   "card-grid",
   "eve"
  ],
  "v1-1-release": [
   "card-grid",
   "eve"
  ],
  "v1-1-acceptance": [
   "card-grid",
   "eve"
  ],
  "v1-2-restoration": [
   "card-grid",
   "eve"
  ],
  "metis-v1-2-readiness": [
   "step-journey",
   "eve"
  ]
 }
}

The release scope, declared once#

git show b6f1ccf1c111:libs/oshun/navigation/src/release-scope.ts, lines 32 to 58:

text
   32  export const LILITH_CURRENT_RELEASE = 'V1.0';
   33  
   34  /** Release that adds the native iOS/Android apps (`LILITH_NATIVE_APPS_AVAILABLE`). */
   35  export const LILITH_NATIVE_APPS_RELEASE_NAME = 'V1.1';
   36  
   37  /** Release that restores Veritas and Metis to the shell. */
   38  export const V1_DEFERRED_DOMAIN_RELEASE = 'V1.2';
   39  
   40  /**
   41   * Rooms held back from V1.0 and V1.1. Canonical registry order.
   42   */
   43  export const V1_DEFERRED_DOMAIN_IDS = [
   44    'veritas',
   45    'metis',
   46  ] as const satisfies readonly OshunDomain[];
   47  
   48  export type V1DeferredDomainId = (typeof V1_DEFERRED_DOMAIN_IDS)[number];
   49  
   50  /**
   51   * Rooms Lilith actually ships in V1.0, in canonical registry order.
   52   *
   53   * The `satisfies` clause below pins this list to exactly `OshunDomain` minus
   54   * the deferred rooms, so adding a seventh domain without placing it on one
   55   * side of the cut is a type error rather than a silently missing room.
   56   */
   57  export const V1_SCOPED_DOMAIN_IDS = [
   58    'tara',

git show b6f1ccf1c111:libs/oshun/navigation/src/release-scope.ts, lines 76 to 84:

text
   76  export interface DeferredDomainNotice {
   77    domainId: V1DeferredDomainId;
   78    /** Display name, e.g. `Veritas`. */
   79    displayName: string;
   80    /** Release that restores the room. */
   81    release: string;
   82    /** Short headline for an empty state or status banner. */
   83    headline: string;
   84    /** One-sentence explanation shown to a member who reached the room. */

The brand record: three releases, and what the deferral is#

git show b6f1ccf1c111:V1/BRAND.md, lines 82 to 116:

text
   82  ## V1 release scope (2026-08-05)
   83  
   84  The V1 line ships in three releases. Say **V1.0** rather than bare "V1" in copy
   85  and docs — "V1" alone reads as the whole line and wrongly implies the deferred
   86  pieces are gone for good.
   87  
   88  | Release  | What it adds                                                           |
   89  | -------- | ---------------------------------------------------------------------- |
   90  | **V1.0** | Web + PWA. Four rooms: Tara, Nyx, Arete, Nisaba. Crypto payments only. |
   91  | **V1.1** | Native iOS/Android apps, the watch companions, and the fiat rails.     |
   92  | **V1.2** | Restores the Veritas and Metis rooms.                                  |
   93  
   94  - **V1.0 ships web + PWA only.** The Next.js customer web app at
   95    `lilith.oshunsynthetics.com` and its installable PWA are the launch surfaces.
   96  - **V1.0 ships four rooms.** Veritas and Metis are deferred to **V1.2**. Their
   97    libraries, contracts, routes, and BFF services all stay in the tree — the
   98    deferral is about what a console may show, not about deleting a domain. No
   99    console (customer web, PWA, mobile, operator, studio, tenant, marketing) may
  100    advertise, link to, count, or compose them.
  101  
  102    The cut is declared once, in `libs/oshun/navigation/src/release-scope.ts`
  103    (`V1_DEFERRED_DOMAIN_IDS`, re-exported from `@oshun/domain-registry`), and
  104    every surface reads it. Lifting the deferral in V1.2 is one edit there plus
  105    the copy that quotes the release name. Enforcement points worth knowing:
  106    - `getShellNavigationDomains()` / `getAvailableDomains()` — scoped selectors
  107      every nav surface uses; `listDomainMetadata()` stays complete for admin.
  108    - `apps/oshun/web/src/middleware.ts` — rewrites deferred page paths to the
  109      `/release-scope/<domain>` notice and 404s the app's own API handlers.
  110    - `apps/oshun/bff/src/middleware/release-scope.ts` — 404s customer-facing
  111      deferred paths; operator/admin/studio paths are exempt so governance can
  112      keep stocking the rooms before they open.
  113    - `WALKTHROUGH/matrix/routes.csv` — those routes are marked `out-of-v1`.
  114  
  115  - **V1.0 charges through crypto only.** The Aje crypto rail (`/billing/crypto`)
  116    is the single rail V1.0 bills on. Card, bank, wallet, PayPal, mobile-money,

The Eve handbook's status vocabulary#

git show b6f1ccf1c111:V1/docs/eve/README.md, lines 124 to 138:

text
  124  ## Status vocabulary
  125  
  126  Eve documentation distinguishes four kinds of truth:
  127  
  128  - **Shipped / wired** means a user-reachable path and its enforcement exist.
  129  - **Built but unwired** means code exists but the supported product path does
  130    not call it.
  131  - **Gated** means the path exists only behind configuration, credentials, tenant
  132    policy, release scope, or explicit operator approval.
  133  - **Proposed / backlog** means a design or task exists without a shipped claim.
  134  
  135  The handbook describes architecture and invariants. Date-stamped audit and TODO
  136  documents remain the source of truth for completion state. Never infer shipment
  137  from a type, tool description, route stub, or backlog checkbox alone.
  138  

The charter completeness record on its own evidence#

git show b6f1ccf1c111:docs/audits/EVE_SOTA_CHARTER_COMPLETENESS_2026-09.md, lines 140 to 146:

text
  140  ## Evidence boundary
  141  
  142  - This record ratifies source coverage and workflow ownership only; it does not
  143    claim any required product capability, runtime, release, or charter workflow
  144    delivered.
  145  - Every required workflow remains blocked until the actual runtime and human
  146    acceptance evidence passes tasks 11.8 and 12.8.

git show b6f1ccf1c111:docs/audits/EVE_SOTA_CHARTER_COMPLETENESS_2026-09.md, lines 130 to 138:

text
  130  ## No closure with unresolved blockers
  131  
  132  No licence, credential, cloud-spend decision, runtime availability observation,
  133  release timing, risk waiver, or accepted limitation closes a required workflow.
  134  Each blocked row retains its owner and exact unblock condition. A verified
  135  alternative may replace a tool only when it preserves and passes the same
  136  source-bound outcome; it cannot erase the outcome. Source drift invalidates
  137  coverage ratification until an independent delta review updates the pinned
  138  source, requirement, workflow, ruleset, platform, and product-graph digests.

How the web application refuses a deferred room#

The brand record names apps/oshun/web/src/middleware.ts; at the pin the file is apps/oshun/web/src/proxy.ts.

git show b6f1ccf1c111:apps/oshun/web/src/proxy.ts, lines 437 to 457:

text
  437   * V1.0 ships four rooms. Veritas and Metis are deferred to V1.2 — their route
  438   * trees, components, and services all stay in the tree, but no request may
  439   * reach them from a console until the deferral lifts.
  440   *
  441   * Nav, rails, search, sitemap, and the PWA shell already omit the deferred
  442   * rooms (see `navigation/release-scope.ts` and its consumers), so nothing in
  443   * the product links here. This is the backstop that also covers bookmarks,
  444   * crawlers, hand-typed URLs, and any subroute added later:
  445   *
  446   * - page requests redirect to `/release-scope/<domain>`, which explains the
  447   *   deferral and offers the rooms that are open. A redirect rather than a
  448   *   rewrite: the browser URL has to leave the room's path, or the shell's
  449   *   client-side auth guard still sees a protected pathname and bounces the
  450   *   notice to /welcome — and a 200 on a room URL invites indexing;
  451   * - the app's own `/api/<domain>/*` handlers refuse with 404 and the
  452   *   machine-readable reason, so a client cannot read deferred data even if it
  453   *   still holds a cached route.
  454   *
  455   * Runs before auth: whether a room ships in this release is not a permission
  456   * question, and answering it first keeps the refusal identical for everyone —
  457   * a sign-in prompt would both leak that the route is real and send a bookmark

What a deferred room answers, 7 October 2026#

One Next dev server for the member web application (E2E_WEB_ONLY=1, no BFF, no sign-in), checkout d2f35444173c7e69e8632b2db4e17d72b16d6a66, driven once by a Playwright spec that was then removed. A request for the application's own API path under the deferred room is answered 404 with the reason in the body and in a header; a request for the room's page ends at the release-scope notice.

text
GET /api/metis/courses
STATUS 404
HEADER x-release-scope domain_deferred_to_v1_2
BODY {"message":"metis is not part of this release","reason":"domain_deferred_to_v1_2","release":"V1.2"}
FINAL_URL http://127.0.0.1:3010/release-scope/metis
  1 passed (17.6s)

What was not kept#

No release record was examined and no acceptance decision was made. The BFF's refusal of deferred paths was not exercised here (the chapter on Metis learning compared its rule with the code). The draft render's measurements and the axe results are in the record directory named above, not in this document.