@owlmeans/viable-common 0.0.33 → 0.0.34

package/README.md

@@ -21,7 +21,7 @@ filesystem, no inference SDK. It is safe to import from a browser bundle.
 ## Installation
 
 ```bash
-bun add @owlmeans/viable-common@^0.0.33
+bun add @owlmeans/viable-common@^0.0.34
 ```
 
 ## Rules worth knowing before you change something
@@ -39,7 +39,7 @@ means "inherit" has no other spelling. `tests/convert.spec.ts` walks every expor
 both faults, and for draft-04 tuple `items`.
 
 **A field that crosses a version skew carries no `enum`.** A connector is installed with
-`npx -y @owlmeans/viable-mcp@^0.1.18-rc.30` and talks to a separately deployed platform, so an executor kind it
+`npx -y @owlmeans/viable-mcp@^0.1.18-rc.31` and talks to a separately deployed platform, so an executor kind it
 sends must remain an unused capability on an older platform rather than a refused session.
 
 **A ceiling exists once.** The inquiry answer cap here equals `DEFAULT_INQUIRY_ANSWER_CHARS` in
@@ -59,7 +59,7 @@ This package ships embedded agent skills under `agent-meta/`. After installing y
 your project's skill store (`.agents/skills/`):
 
 ```sh
-npx @owlmeans/agent-skills@^0.1.18-rc.38
+npx @owlmeans/agent-skills@^0.1.18-rc.39
 ```
 
 The embedded files are version-matched to this package release. Do not edit them

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/viable-common",
-  "version": "0.0.33",
-  "generatedAt": "2026-09-23T19:57:40.697Z",
+  "version": "0.0.34",
+  "generatedAt": "2026-09-24T14:00:40.411Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/agent-presentation/SKILL.md

@@ -6,7 +6,7 @@ description: Shared, runtime-free taxonomy for presenting OwlMeans Viable agent
 
 # Agent output presentation
 
-**Install:** `"@owlmeans/viable-common": "^0.0.33"` in `dependencies`
+**Install:** `"@owlmeans/viable-common": "^0.0.34"` in `dependencies`
 
 `@owlmeans/viable-common`'s `agent/presentation.ts` owns the browser-safe vocabulary for agent
 output. Keep the server and every client on `classifyAgentMessage()`; consumers may refine a

package/agent-meta/skills/viable-common/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: viable-common
-description: How to use @owlmeans/viable-common — the runtime-free contract package of the OwlMeans Viable platform. Covers planning cards and flows (including the landing-gate fields), project/story refusals, slot commands and layouts, slot metadata keys, target integrity, connector domain statuses and routes, conversion vocabulary, blueprint layers and cases, the persona/skill catalogue and its design house style, generated-project analysis/design/scaffold/metadata shapes, StoryDesignPort, schema conventions, and wire-version rules. Auto-invoked when importing a viable card type or flow, a slot command, a connector or conversion type, a target-integrity helper, or any *Schema this package exports.
+description: How to use @owlmeans/viable-common — the runtime-free contract package of the OwlMeans Viable platform. Covers planning cards and flows (including the landing-gate fields), project/story refusals, slot commands and layouts, slot metadata keys, target integrity, connector domain statuses and routes, the intent-first hand-off (`./intent`), conversion vocabulary, blueprint layer types and the case vocabulary, the ViableSkill/ViablePersona names (never the catalogue behind them), what belongs here versus in @owlmeans/viable, generated-project analysis/design/scaffold/metadata shapes, StoryDesignPort, schema conventions, and wire-version rules. Auto-invoked when importing a viable card type or flow, a slot command, a connector or conversion type, a target-integrity helper, or any *Schema this package exports.
 user-invocable: false
 ---
 <!-- AUTO-GENERATED — do not edit. Regenerate via sync-agent-meta. -->
@@ -8,12 +8,13 @@ user-invocable: false
 # @owlmeans/viable-common
 
 **Layer:** Cross-cutting domain (contracts only)
-**Install:** `"@owlmeans/viable-common": "^0.0.33"` in `dependencies`
-**Subpaths:** `.` · `./slot` · `./connect` · `./convert` · `./integrity`
+**Install:** `"@owlmeans/viable-common": "^0.0.34"` in `dependencies`
+**Subpaths:** `.` · `./slot` · `./connect` · `./convert` · `./integrity` · `./intent`
 **Runtime-free:** no `@langchain/*`, no filesystem, no Ajv at run time (a devDependency, for the
 tests that compile the schemas). It depends on `@owlmeans/planning`, `@owlmeans/resource`,
-`@owlmeans/entrypoint`, `@owlmeans/route`, `@owlmeans/error`, `@owlmeans/agent-common` and
-`@owlmeans/llm-common` and on nothing else.
+`@owlmeans/entrypoint`, `@owlmeans/route`, `@owlmeans/error`, `@owlmeans/agent-common`,
+`@owlmeans/llm-common` and — for `./intent` alone — `@owlmeans/flow`, `@owlmeans/auth` and
+`@owlmeans/context`, and on nothing else.
 
 Every name the OwlMeans Viable platform puts on a wire, on a volume or in a prompt is declared
 here once, and the four runtimes that must agree about it — the manager API, the agent, the
@@ -21,15 +22,24 @@ publisher/production runtime, and the connector SDK on somebody's laptop — all
 declaration. A vocabulary copied instead of imported is how one tree gets two totals, one
 refusal two spellings, and one ceiling two values.
 
+**Names, not agent-only data.** This package is imported by the BROWSER too, so everything in it
+ships in every visitor's bundle. Prompt, persona and blueprint-case DATA that only the AI agent
+library ever reads — never the browser or another server package — belongs in `@owlmeans/viable`
+instead: the skill bodies and their order, the persona prompt
+policies, the blueprint case table and resolution, the BA model-answer schemas. What stays here is
+what another package's contract references by type — the `ViableSkill` / `ViablePersona` enums and
+the `Blueprint` types and vocabulary that execution state and card fields name.
+
 ## Key Exports
 
 | Subpath | What it declares |
 |---|---|
-| `.` (barrel) | The planning module (`VIABLE_*_TYPE`, `VIABLE_TYPE_SCHEMAS`, `VIABLE_FLOW_SCHEMAS`, `ViableStoryStatus`/`ViableProjectStatus` and their transitions, `ViableSpecCategory`, `ViableRelationship`, `ViableChannel`, `ViableProjectCard`/`ViableStoryCard`, the card helpers, the landing sentence helpers, the `Project*` refusals); `SlotMetadata` and the three metadata vocabularies (`metadataConfigs`, `metadataLists`, `metadataSecrets`), `BRANDING_ENV_KEYS` / `brandingEnv`; `ProjectArea` / `AREA_PATHS` / `AREA_ACCESS` / `AREA_TIER`; `ModelRole` and the viable `ExecutionState`; `ViableSkill` / `ViablePersona` / `VIABLE_SKILLS`; the blueprint, its cases and `landingGatePreferenceOf`; the BA, dev, UX, design and scaffold shapes and their schemas, `StoryDesignPort`; `ModerationCategory` / `ModerationSubject` / `decideModeration`; the `docs/` metadata paths; `PreviewEventType` |
+| `.` (barrel) | The planning module (`VIABLE_*_TYPE`, `VIABLE_TYPE_SCHEMAS`, `VIABLE_FLOW_SCHEMAS`, `ViableStoryStatus`/`ViableProjectStatus` and their transitions, `ViableSpecCategory`, `ViableRelationship`, `ViableChannel`, `ViableProjectCard`/`ViableStoryCard`, the card helpers, the landing sentence helpers, the `Project*` refusals); `SlotMetadata` and the three metadata vocabularies (`metadataConfigs`, `metadataLists`, `metadataSecrets`), `BRANDING_ENV_KEYS` / `brandingEnv`; `ProjectArea` / `AREA_PATHS` / `AREA_ACCESS` / `AREA_TIER`; `ModelRole` and the viable `ExecutionState`; the `ViableSkill` / `ViablePersona` enums (names only); the `Blueprint` layer types, `BlueprintRef` / `BlueprintPatch`, `BlueprintCase` / `GameKind`, `DEFAULT_BLUEPRINT_ID` / `BLUEPRINT_META_KEY` and `landingGatePreferenceOf`; the BA shapes and helpers (`mergeConnectingStories`), the dev, UX, design and scaffold shapes and their schemas, `StoryDesignPort`; `ModerationCategory` / `ModerationSubject` / `decideModeration`; the `docs/` metadata paths; `PreviewEventType` |
 | `./slot` | `SlotCommandType` and the `SlotFileCommand` / `SlotShellCommand` / `SlotGitCommand` sets, `SubProject`, `WorkloadKind`, the target ports and process markers, `slotOrigin` / `targetRedirectUrisForOrigin` |
 | `./connect` | `ConnectTarget`, `ConnectLlm`, `ConnectHarness`, `ConnectExecutor`, `ConnectOpKind`, `ConnectProjectStatus`, `ConnectStoryStatus`, `ConnectPipelineState`, `ConnectWaitReason`, `ConnectProjectBranding` / `ConnectProjectBrandingSave`, `ModelTier` + `tierOfRole`/`clampTier`, `ModelTask*`, `InquiryPayload` + `ConnectInquiryKind`, the session and domain-status views, the `Connect*` error family, `connectProtocols(opts)` and every `*Schema` behind them |
 | `./convert` | `ConversionStage`/`Status`/`Decision` and the `stageAfter`/`decisionFor`/`canEnter` transitions, `OriginKind`/`Shape`/`State`, `StackId` + `STACK_FAMILY`, `ArchitectureCase`, `ConvertibilityVerdict`/`Reason`, the census classifiers (`fileClassOf`, `sizeClassOf`, `entropyClassOf`, `binaryByExtension`), the `docs/conversion/` paths, `CONVERTED_ORIGIN_DIR`, `SOURCE_LIST_EXCLUSIONS`, `CENSUS_SKIP_DIRS`, `RELOCATE_ALWAYS_KEEP`, and the model-answer schemas the conversion asks with |
 | `./integrity` | `TargetLayout` + `TARGET_LAYOUTS`, `detectTargetLayout`, `verifyTargetShape`, `TARGET_INTEGRITY_FILES`, `TARGET_PROTECTED_FILES`, `isLegacyLayout`, `targetPackageName` |
+| `./intent` | The intent-first hand-off from the public site to the platform: `intent` (the four aliases), `makeIntentProtocols(opts?)` (two GUEST API routes + the `/start` landing screen), `intentFlow` + `IntentFlowStep` + `INTENT_PAYLOAD_REF`, `IntentStashBodySchema` / `IntentPickupBodySchema`, the `INTENT_*` constants (TTL, prompt cap, reference pattern, draft and suspend windows), `IntentDraft`, `IntentExpired` (404) / `IntentThrottled` (429) |
 
 ## The planning module
 
@@ -253,7 +263,7 @@ code, never as `minItems`/`maxItems`. The descriptions are what the planning mod
 state each field's purpose and bounds; `gate.target` is filled by code and described as such.
 
 **A field that crosses a version skew carries no `enum`.** Users run
-`npx -y @owlmeans/viable-mcp@^0.1.18-rc.30` (the moving prerelease tag) against a separately deployed
+`npx -y @owlmeans/viable-mcp@^0.1.18-rc.31` (the moving prerelease tag) against a separately deployed
 platform, so `ConnectCapabilitiesSchema.executors.items`
 is a bare string: a newer executor kind must stay an unused capability on an older platform, never
 a refused session. Apply the same reasoning to anything else a newer connector may send an older
@@ -295,6 +305,45 @@ pending inquiry and `waitingFor` reason; none exposes a generic technical operat
 new long-running domain by extending its status view and endpoint, not by adding a parallel polling
 vocabulary.
 
+## The intent-first hand-off (`./intent`)
+
+A prompt typed on the PUBLIC site (owlmeans.com, a static Astro app that cannot import the platform
+repo) reaches the platform through this one subpath, which is why it lives here and not in viable:
+the site, the manager API and the manager web must agree on every address, schema and step.
+
+- **Two guest routes and one screen, no guard, no gate, no service.** `makeIntentProtocols()` declares
+  `stash` (POST `/public/intent`, body `{ prompt 1..8192, consent: const true }` → `{ ref, expiresAt }`),
+  `pickup` (POST `/public/intent/pickup`, body `{ ref }` where `ref` is exactly `createIdOfLength(24)`
+  Base58 → `{ prompt }`) and `landing` (`frontend()` at `/start`, `sticky`). A consumer mounts the
+  tree OUTSIDE any guarded parent — a route inherits every ancestor's guard, so under the account
+  base a visitor with no account would be refused — and fills `service` itself (the site binds
+  `landing` with `{ routeOptions: { overrides: { service } } }`, which is also what makes its `url()`
+  absolute). `consent` is a schema constant so a request without the data-processing confirmation
+  cannot exist on the wire.
+- **The prompt never travels in a URL or a flow token.** The server keeps it `INTENT_TTL_SECONDS`
+  (120) under the unguessable `ref`, and collects it with one `GETDEL` (`pickup`); only `?ref=`
+  crosses. The flow payload is CSV-joined without escaping and the token is unsigned, so the flow
+  carries the reference or nothing.
+- **`intentFlow` is walked on both sides and never becomes the live flow model.** `compose`
+  (initial, the site) →`handoff`→ `land` (initial, module = the landing) →`review`→ `review`
+  (module `HOME`), plus the EXPLICIT `land` →`sign-in`→ `sign-in` (module `DISPATCHER`) →`next`→
+  `review`. The site does `transit('handoff', true, { ref })` and redirects to `land`'s module URL
+  with the payload as query; the landing enters at `land` fresh, and a signed-out visitor is parked
+  with `suspendFlow` at `sign-in`, whose `next()` is the home screen. The parameter is `?ref=` —
+  never `?flow=`, which `web-flow`'s `lazyInit` parses on every page load of an app that registered
+  the flow service, and never `?intent=`, which the login surrogate window owns.
+- **CORS is not declared here.** The routes ride the framework's global `origin: '*'` (no
+  credentials); `makeIntentProtocols` carries a `TODO(cors)` naming the origins to keep allowed if a
+  deployment ever restricts them globally.
+- **The browser draft is IndexedDB, per origin.** `IntentDraft` (`id`, `ref`, `prompt`, `expiresAt`) is
+  what the platform's own browser keeps between pickup and the decision (`INTENT_DRAFT_TTL_MS`, 24 h,
+  checked on read — a client resource has no TTL). The public site cannot write it; that is the whole
+  reason for the server detour.
+
+Tests: `tests/intent.spec.ts` (the four declarations and their absence of guards, the schema
+accept/reject cases including crafted references, the flow walk both sides and what `suspendFlow`
+would persist, the error statuses).
+
 ## Slot metadata keys: optional means omitted
 
 `SlotMetadata` is what the platform signs and pushes into a slot, and a slot publisher validates it
@@ -311,55 +360,36 @@ an owner setting, so it is declared on the type and kept out of them. The Google
 never travel in it: the publisher derives them from `brandingGoogleTag` itself (and from the record a
 production build writes), so the tag and the hosts it needs cannot disagree.
 
-## Blueprint layers and the case table
-
-A `Blueprint` has five REQUIRED build layers (`technology`, `stack`, `template`, `createApp`,
-`packages`) and one OPTIONAL `experience` layer — what the product should do for its users,
-changing no dependency and no coder prompt. Read it only through a helper that answers the default
-for an absent layer: `landingGatePreferenceOf(blueprint)` answers `LandingGatePreference.Allow` for
-no layer, no key or a value this deploy does not know. `freezeBlueprint` freezes the layer when
-present and never adds it when absent.
-
-The preference is a PRIOR for the model that decides the landing gate, never the decision:
-
-| Case | `experience.landingGate` | `ViableSkill.LandingGate` added to |
-|---|---|---|
-| `web`, `ai-pipeline`, `ai-agent` | `encourage` | `BusinessAnalyst`, `UxDesigner`, `LayoutArchitect`, `ComponentArchitect`, `UiViewCoder`, `UiNavCoder` |
-| `scalable` | `allow` | — |
-| `game` | `discourage` | — |
-
-A case's `personaSkills` are composed with `joinPersonaSkills`, which UNIONS a persona two maps
-both name — an object spread keeps only the last list and silently drops the other case's skill.
-`applyBlueprintCase` then unions the case's persona skills with the base blueprint's.
-
-## The design house style in the catalogue
-
-The `VisualDesigner` persona and the `ShadcnUi` skill teach one house style, and the template seed
-ships the same values: a white ground (black in dark mode) on `bg-background`; colour from ONE
-product accent, never from a background; depth only from a hairline, the neutral tile (`bg-muted`)
-and one `shadow-floating`; a heavy grotesk display face with tight tracking; motion that belongs
-to the illustration. The older classes (`gradient-heading`, `glass-card`, `eyebrow`, `glow-orb`,
-the soft/raised/glow shadows, `pulse-soft`, `spin-slow`) stay DEFINED because existing targets use
-them, are repainted flat, and are never taught as decoration. Any of it changes only when the
-customer's specification explicitly asks — a named background colour, a dark-only or coloured
-theme, a brand palette, gradients; the product's subject matter is not a request.
-`tests/skills.spec.ts` pins both texts against drifting back.
-
-`ViableSkill.LandingGate` teaches the gate-worthy story, the gate card, the synchronous handoff
-(`useLandingStart(target)` from the seed's `@/lib/handoff`: write, then navigate when signed in or
-start the plain sign-in; the guest home's `useLandingContinuation` sends the visitor on after
-sign-in — never `useLogin(target)`, whose continuation lands on the guarded screen) and the
-full-scale screen that reads and clears it. Every `ViableSkill` member has a body in `VIABLE_SKILLS` and a weight in
-`SKILL_ORDER`: the prompt service skips an alias it cannot resolve, so a missing body is a rule no
-model ever receives.
-
-`OwlMeansServer` and `FixerHeuristics` teach one rule from both ends: the PROTOCOL decides a
-handler's types. A handler's parameter and return types are exactly what its declaration in the
-target's shared entrypoints module names, imported from the shared package — never an input or
-record type declared in the api or backend package, which the shared package cannot import. The
-example handler therefore takes the shared `Task`, never an invented `…Payload`/`…Input` type
-(an example wins over the rule beside it), and a `TS2345` function-vs-function mismatch at a binding
-line is repaired in the HANDLER, never by bending the declaration toward it.
+## Blueprint types and the case vocabulary
+
+`src/blueprint/` holds only types and constants. A `Blueprint` has five REQUIRED build layers
+(`technology`, `stack`, `template`, `createApp`, `packages`) and one OPTIONAL `experience` layer —
+what the product should do for its users, changing no dependency and no coder prompt. Read it only
+through a helper that answers the default for an absent layer: `landingGatePreferenceOf(blueprint)`
+answers `LandingGatePreference.Allow` for no layer, no key or a value this deploy does not know.
+An execution carries a `BlueprintRef` — an id, an optional `case` and an override patch — never a
+resolved blueprint.
+
+`BlueprintCase` (`web`, `scalable`, `ai-pipeline`, `ai-agent`, `game`) and `GameKind` are the
+vocabulary a project card's `fields.blueprintCase` / `fields.gameKind` carry. What a case MEANS —
+the `BLUEPRINT_CASES` table with each case's patch, landing-gate prior and persona skills,
+`applyBlueprintCase`, `applyBlueprintPatch` / `freezeBlueprint`, `joinPersonaSkills` and the
+classification schema — lives in `@owlmeans/viable` (its `blueprints` / `blueprint-cases` skills).
+That table is typed `Record<BlueprintCase, …>`, so a member added here fails to compile there until
+it has a row.
+
+## Skill and persona names
+
+`src/skills/` holds two enums and nothing else: `ViableSkill` (prompt-skill aliases) and
+`ViablePersona` (who a helper's model is told it is). They are here because a `Blueprint`'s
+`stack.skills` / `packages.skills` / `personaSkills` name them. The catalogue behind them — every
+skill body (`VIABLE_SKILLS`) and weight (`SKILL_ORDER`), `FRAMEWORK_OWNED_SKILLS` /
+`skillsForBlueprint`, each persona's prompt policy (`VIABLE_PERSONAS`), the design house style and
+the landing-gate teaching — lives in `@owlmeans/viable` `src/skills/` (its `personas-and-skills`
+skill). Adding a member here is half a change: `SKILL_ORDER` and `VIABLE_PERSONAS` are total records
+and fail to compile until the new member has a weight or a policy, but `VIABLE_SKILLS` is a list,
+and the prompt service skips an alias it cannot resolve — a missing body is a rule no model ever
+receives.
 
 ## Closed sets that mean something
 
@@ -463,10 +493,8 @@ the field schemas accepting `null` and refusing an undeclared field or a value o
 set, the landing fields and the landing sentence, the card helpers, the `follows` anchor, and the
 refusals' type names surviving a marshal), `scaffold.spec.ts` (an old-shape and a new-shape plan
 both passing the schema and the `scaffold` slot, `null` optionals accepted, no `minItems`),
-`blueprint.spec.ts` (each case's gate preference, the default, and the persona-skill unions),
-`branding.spec.ts` (the build env and the metadata vocabulary), `skills.spec.ts` (every skill has a
-body and a weight, the handler wrap-once teaching, handler types taken from the protocol and the
-mismatch repaired in the handler, the house style and the landing-gate skill),
+`blueprint.spec.ts` (`landingGatePreferenceOf` — the default for an absent layer or an unknown
+value), `branding.spec.ts` (the build env and the metadata vocabulary),
 `connect-entrypoints.spec.ts` (the tree's protocol count, no story route, the job-id round trip,
 the branding routes and their save body),
 `convert.spec.ts` (the three structural walks over the barrel, the
@@ -486,14 +514,17 @@ marshal round trip), `connect-errors.spec.ts` (the packed fields of `ConnectOutO
 - `@owlmeans/resource` — the `ResourceError` base of the project refusals
 - `@owlmeans/entrypoint`, `@owlmeans/route` — the entrypoint declarations
 - `@owlmeans/error` — the `Connect*` error family
-- `@owlmeans/llm-common` — `ExecutionEffort`/`ExecutionLevel`, `PromptPolicy`, `LlmPurpose`, and the
-  inquiry ceilings this package's copies are pinned to
+- `@owlmeans/llm-common` — `ExecutionEffort`/`ExecutionLevel`, `LlmPurpose`, the spectator
+  contracts, and the inquiry ceilings this package's copies are pinned to
 - `@owlmeans/agent-common` — the run and pipeline contracts a conversion's runs are declared against
+- `@owlmeans/flow`, `@owlmeans/auth`, `@owlmeans/context` — `./intent` only: `ShallowFlow`/`UnknownFlow`,
+  the `DISPATCHER` alias and the `HOME` alias its flow steps address
 
 ## Related
 
 - [[viable-sdk]] — the connector SDK written entirely against these contracts
 - [[viable-mcp]] — the npx stdio server built on that SDK
+- [[flow]] · [[client-flow]] — the model `intentFlow` is walked with, and `suspendFlow`, which parks it across sign-in
 - [[inquiry]] — the primitive `InquiryPayload` mirrors, and the one answer ceiling
 - [[llm-common]] — the contracts half of the model runtime
 - [[planning]] — the workcard model, flows, fold and protocol tree the planning module builds on

package/build/ba/index.d.ts

@@ -1,4 +1,3 @@
-export * from './schemas.js';
 export * from './helpers.js';
 export * from './consts.js';
 export type * from './types.js';

package/build/ba/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/ba/index.ts"],"names":[],"mappings":"AACA,cAAc,cAAc,CAAA;AAC5B,cAAc,cAAc,CAAA;AAC5B,cAAc,aAAa,CAAA;AAC3B,mBAAmB,YAAY,CAAA"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/ba/index.ts"],"names":[],"mappings":"AACA,cAAc,cAAc,CAAA;AAC5B,cAAc,aAAa,CAAA;AAC3B,mBAAmB,YAAY,CAAA"}

package/build/ba/index.js

@@ -1,4 +1,3 @@
-export * from './schemas.js';
 export * from './helpers.js';
 export * from './consts.js';
 //# sourceMappingURL=index.js.map

package/build/ba/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/ba/index.ts"],"names":[],"mappings":"AACA,cAAc,cAAc,CAAA;AAC5B,cAAc,cAAc,CAAA;AAC5B,cAAc,aAAa,CAAA"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/ba/index.ts"],"names":[],"mappings":"AACA,cAAc,cAAc,CAAA;AAC5B,cAAc,aAAa,CAAA"}

package/build/blueprint/consts.d.ts

@@ -8,4 +8,42 @@
 export declare const DEFAULT_BLUEPRINT_ID = "owlmeans-fullstack-ts";
 /** Recorded on a project so a later run knows which blueprint drew it. */
 export declare const BLUEPRINT_META_KEY = "blueprint";
+/**
+ * WHICH KIND of product is being built on a blueprint.
+ *
+ * A blueprint says what the STACK is — the language, the framework, the topology, the seeds. A
+ * case says what is being built ON it, and that is a different question with different consumers:
+ * the analyst framing the brief, the architect deciding whether a story needs a queue, the coder
+ * choosing which packages it may import.
+ *
+ * Deliberately NOT a second blueprint. Everything a case has to say is already a blueprint field,
+ * so a case is a PATCH and the resolution order stays base → case → per-run overrides. That is
+ * also why adding one is a data change: nothing reads `BlueprintCase` except the case table
+ * (`BLUEPRINT_CASES` in `@owlmeans/viable`) and the prompt that classifies a project into it.
+ */
+export declare enum BlueprintCase {
+    /** A web application whose every feature fits inside a request. No queue, no worker, no agents. */
+    Web = "web",
+    /** A web application with work that genuinely belongs off the request path. */
+    Scalable = "scalable",
+    /** The product's value comes from ordered, deterministic model-driven steps. */
+    AiPipeline = "ai-pipeline",
+    /** The product's value comes from an agent that decides its own path through tools. */
+    AiAgent = "ai-agent",
+    /** A browser game: a three.js scene with an ordinary React interface over it. */
+    Game = "game"
+}
+/**
+ * How a game is played, which decides who owns its state.
+ *
+ * Recorded beside the case rather than folded into it, because it changes nothing about the
+ * dependencies and everything about where the logic goes. `OnlineTurn` is the default for
+ * anything multiplayer unless the brief plainly asks for live play — it is the shape that
+ * actually builds, and it needs no socket, no tick loop and no reconciliation.
+ */
+export declare enum GameKind {
+    Casual = "casual",
+    OnlineTurn = "online-turn",
+    OnlineLive = "online-live"
+}
 //# sourceMappingURL=consts.d.ts.map

package/build/blueprint/consts.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"consts.d.ts","sourceRoot":"","sources":["../../src/blueprint/consts.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,eAAO,MAAM,oBAAoB,0BAA0B,CAAA;AAE3D,0EAA0E;AAC1E,eAAO,MAAM,kBAAkB,cAAc,CAAA"}
+{"version":3,"file":"consts.d.ts","sourceRoot":"","sources":["../../src/blueprint/consts.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,eAAO,MAAM,oBAAoB,0BAA0B,CAAA;AAE3D,0EAA0E;AAC1E,eAAO,MAAM,kBAAkB,cAAc,CAAA;AAE7C;;;;;;;;;;;;GAYG;AACH,oBAAY,aAAa;IACvB,mGAAmG;IACnG,GAAG,QAAQ;IACX,+EAA+E;IAC/E,QAAQ,aAAa;IACrB,gFAAgF;IAChF,UAAU,gBAAgB;IAC1B,uFAAuF;IACvF,OAAO,aAAa;IACpB,iFAAiF;IACjF,IAAI,SAAS;CACd;AAED;;;;;;;GAOG;AACH,oBAAY,QAAQ;IAClB,MAAM,WAAW;IACjB,UAAU,gBAAgB;IAC1B,UAAU,gBAAgB;CAC3B"}

package/build/blueprint/consts.js

@@ -8,4 +8,44 @@
 export const DEFAULT_BLUEPRINT_ID = 'owlmeans-fullstack-ts';
 /** Recorded on a project so a later run knows which blueprint drew it. */
 export const BLUEPRINT_META_KEY = 'blueprint';
+/**
+ * WHICH KIND of product is being built on a blueprint.
+ *
+ * A blueprint says what the STACK is — the language, the framework, the topology, the seeds. A
+ * case says what is being built ON it, and that is a different question with different consumers:
+ * the analyst framing the brief, the architect deciding whether a story needs a queue, the coder
+ * choosing which packages it may import.
+ *
+ * Deliberately NOT a second blueprint. Everything a case has to say is already a blueprint field,
+ * so a case is a PATCH and the resolution order stays base → case → per-run overrides. That is
+ * also why adding one is a data change: nothing reads `BlueprintCase` except the case table
+ * (`BLUEPRINT_CASES` in `@owlmeans/viable`) and the prompt that classifies a project into it.
+ */
+export var BlueprintCase;
+(function (BlueprintCase) {
+    /** A web application whose every feature fits inside a request. No queue, no worker, no agents. */
+    BlueprintCase["Web"] = "web";
+    /** A web application with work that genuinely belongs off the request path. */
+    BlueprintCase["Scalable"] = "scalable";
+    /** The product's value comes from ordered, deterministic model-driven steps. */
+    BlueprintCase["AiPipeline"] = "ai-pipeline";
+    /** The product's value comes from an agent that decides its own path through tools. */
+    BlueprintCase["AiAgent"] = "ai-agent";
+    /** A browser game: a three.js scene with an ordinary React interface over it. */
+    BlueprintCase["Game"] = "game";
+})(BlueprintCase || (BlueprintCase = {}));
+/**
+ * How a game is played, which decides who owns its state.
+ *
+ * Recorded beside the case rather than folded into it, because it changes nothing about the
+ * dependencies and everything about where the logic goes. `OnlineTurn` is the default for
+ * anything multiplayer unless the brief plainly asks for live play — it is the shape that
+ * actually builds, and it needs no socket, no tick loop and no reconciliation.
+ */
+export var GameKind;
+(function (GameKind) {
+    GameKind["Casual"] = "casual";
+    GameKind["OnlineTurn"] = "online-turn";
+    GameKind["OnlineLive"] = "online-live";
+})(GameKind || (GameKind = {}));
 //# sourceMappingURL=consts.js.map

package/build/blueprint/consts.js.map

@@ -1 +1 @@
-{"version":3,"file":"consts.js","sourceRoot":"","sources":["../../src/blueprint/consts.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAAG,uBAAuB,CAAA;AAE3D,0EAA0E;AAC1E,MAAM,CAAC,MAAM,kBAAkB,GAAG,WAAW,CAAA"}
+{"version":3,"file":"consts.js","sourceRoot":"","sources":["../../src/blueprint/consts.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAAG,uBAAuB,CAAA;AAE3D,0EAA0E;AAC1E,MAAM,CAAC,MAAM,kBAAkB,GAAG,WAAW,CAAA;AAE7C;;;;;;;;;;;;GAYG;AACH,MAAM,CAAN,IAAY,aAWX;AAXD,WAAY,aAAa;IACvB,mGAAmG;IACnG,4BAAW,CAAA;IACX,+EAA+E;IAC/E,sCAAqB,CAAA;IACrB,gFAAgF;IAChF,2CAA0B,CAAA;IAC1B,uFAAuF;IACvF,qCAAoB,CAAA;IACpB,iFAAiF;IACjF,8BAAa,CAAA;AACf,CAAC,EAXW,aAAa,KAAb,aAAa,QAWxB;AAED;;;;;;;GAOG;AACH,MAAM,CAAN,IAAY,QAIX;AAJD,WAAY,QAAQ;IAClB,6BAAiB,CAAA;IACjB,sCAA0B,CAAA;IAC1B,sCAA0B,CAAA;AAC5B,CAAC,EAJW,QAAQ,KAAR,QAAQ,QAInB"}

package/build/blueprint/index.d.ts

@@ -1,6 +1,3 @@
 export * from './types.js';
 export * from './consts.js';
-export * from './case.js';
-export * from './schemas.js';
-export * from './resolve.js';
 //# sourceMappingURL=index.d.ts.map

package/build/blueprint/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/blueprint/index.ts"],"names":[],"mappings":"AAAA,cAAc,YAAY,CAAA;AAE1B,cAAc,aAAa,CAAA;AAC3B,cAAc,WAAW,CAAA;AACzB,cAAc,cAAc,CAAA;AAC5B,cAAc,cAAc,CAAA"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/blueprint/index.ts"],"names":[],"mappings":"AAAA,cAAc,YAAY,CAAA;AAE1B,cAAc,aAAa,CAAA"}

package/build/blueprint/index.js

@@ -1,6 +1,3 @@
 export * from './types.js';
 export * from './consts.js';
-export * from './case.js';
-export * from './schemas.js';
-export * from './resolve.js';
 //# sourceMappingURL=index.js.map

package/build/blueprint/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/blueprint/index.ts"],"names":[],"mappings":"AAAA,cAAc,YAAY,CAAA;AAE1B,cAAc,aAAa,CAAA;AAC3B,cAAc,WAAW,CAAA;AACzB,cAAc,cAAc,CAAA;AAC5B,cAAc,cAAc,CAAA"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/blueprint/index.ts"],"names":[],"mappings":"AAAA,cAAc,YAAY,CAAA;AAE1B,cAAc,aAAa,CAAA"}

package/build/blueprint/types.d.ts

@@ -171,11 +171,11 @@ export interface PackagesLayer {
     /**
      * Skills added to ONE persona, rather than to every prompt of the blueprint.
      *
-     * The additive twin of {@link skillsForBlueprint}, which subtracts. `skills` above is what is
-     * true of the whole stack; this is what is true of one performer — the analyst who has to know
-     * that a game brief is a core loop rather than a numbered flow, the architect who has to know
-     * when a tool loop is warranted. Without it a case could only change what a CODER is told, and
-     * a case changes the product analysis first.
+     * The additive twin of `skillsForBlueprint` (in `@owlmeans/viable`), which subtracts. `skills`
+     * above is what is true of the whole stack; this is what is true of one performer — the analyst
+     * who has to know that a game brief is a core loop rather than a numbered flow, the architect who
+     * has to know when a tool loop is warranted. Without it a case could only change what a CODER is
+     * told, and a case changes the product analysis first.
      */
     personaSkills?: Partial<Record<ViablePersona, ViableSkill[]>>;
     /** Extra dependencies a role's manifest carries, beyond what the overlay ships. */

package/build/intent/consts.d.ts

@@ -0,0 +1,57 @@
+/**
+ * The intent-first hand-off — how a prompt typed on the public site reaches the platform.
+ *
+ * A visitor types the idea for a project on the marketing site before they have an account. The
+ * site cannot write into the platform's browser storage (IndexedDB is per origin) and must not put
+ * the prompt in a URL, so the prompt takes a short detour through the platform's own cache: the
+ * site stashes it behind an unguessable reference, sends the browser to the platform with only that
+ * reference, and the platform picks the prompt up once — after which it lives in the visitor's own
+ * browser until they decide what to do with it.
+ *
+ * Everything here is serializable and runtime-free: the site, the manager API and the manager web
+ * read the same declarations, and none of them may reinvent a name the others parse.
+ */
+/** Every address of the hand-off. API routes are guest routes; the landing is a screen. */
+export declare const intent: Readonly<{
+    readonly base: 'viable:manager-api:intent:base';
+    readonly stash: 'viable:manager-api:intent:stash';
+    readonly pickup: 'viable:manager-api:intent:pickup';
+    readonly landing: 'viable:manager-web:intent:landing';
+}>;
+/** Where the guest API lives, and the screen the visitor's browser is sent to. */
+export declare const INTENT_API_PATH = "/public/intent";
+export declare const INTENT_LANDING_PATH = "/start";
+/** The flow the two sides walk. */
+export declare const INTENT_FLOW = "viable:intent";
+/**
+ * How long the platform keeps a stashed prompt waiting for pickup. Short on purpose: the pickup
+ * happens the moment the browser lands, so anything older was abandoned, and a prompt is personal
+ * data the platform has no business holding once nobody is coming for it.
+ */
+export declare const INTENT_TTL_SECONDS = 120;
+/** The longest prompt the platform will create a project from (`PromptSchema` in viable). */
+export declare const INTENT_PROMPT_MAX = 8192;
+/**
+ * The reference's shape: `createIdOfLength(24)` — Base58, so no `0`, `O`, `I` or `l`. Anything else
+ * is refused before the cache is asked, which keeps a crafted reference from ever being a key.
+ */
+export declare const INTENT_REF_LENGTH = 24;
+export declare const INTENT_REF_PATTERN = "^[1-9A-HJ-NP-Za-km-z]{24}$";
+/** The flow payload key carrying the reference — short, because a payload is CSV-joined. */
+export declare const INTENT_PAYLOAD_REF = "ref";
+/** How long the visitor's draft survives in their own browser waiting for a decision. */
+export declare const INTENT_DRAFT_TTL_MS: number;
+/** How long a suspended landing waits while the visitor signs in or registers. */
+export declare const INTENT_SUSPEND_TTL_MS: number;
+/** Steps of {@link intentFlow}, exported so a screen never spells one as a literal. */
+export declare enum IntentFlowStep {
+    /** The public site: the prompt is typed and stashed. */
+    Compose = "compose",
+    /** The platform's landing screen: the stash is picked up. */
+    Land = "land",
+    /** The platform's own sign-in dispatcher. */
+    SignIn = "sign-in",
+    /** The platform's home screen, where the draft is offered back. */
+    Review = "review"
+}
+//# sourceMappingURL=consts.d.ts.map

package/build/intent/consts.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"consts.d.ts","sourceRoot":"","sources":["../../src/intent/consts.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,2FAA2F;AAC3F,eAAO,MAAM,MAAM;mBACX,gCAAgC;oBAC/B,iCAAiC;qBAChC,kCAAkC;sBACjC,mCAAmC;EACnC,CAAA;AAEX,kFAAkF;AAClF,eAAO,MAAM,eAAe,mBAAmB,CAAA;AAC/C,eAAO,MAAM,mBAAmB,WAAW,CAAA;AAE3C,mCAAmC;AACnC,eAAO,MAAM,WAAW,kBAAkB,CAAA;AAE1C;;;;GAIG;AACH,eAAO,MAAM,kBAAkB,MAAM,CAAA;AAErC,6FAA6F;AAC7F,eAAO,MAAM,iBAAiB,OAAO,CAAA;AAErC;;;GAGG;AACH,eAAO,MAAM,iBAAiB,KAAK,CAAA;AACnC,eAAO,MAAM,kBAAkB,+BAA+B,CAAA;AAE9D,4FAA4F;AAC5F,eAAO,MAAM,kBAAkB,QAAQ,CAAA;AAEvC,yFAAyF;AACzF,eAAO,MAAM,mBAAmB,QAAsB,CAAA;AAEtD,kFAAkF;AAClF,eAAO,MAAM,qBAAqB,QAAiB,CAAA;AAEnD,uFAAuF;AACvF,oBAAY,cAAc;IACxB,wDAAwD;IACxD,OAAO,YAAY;IACnB,6DAA6D;IAC7D,IAAI,SAAS;IACb,6CAA6C;IAC7C,MAAM,YAAY;IAClB,mEAAmE;IACnE,MAAM,WAAW;CAClB"}

package/build/intent/consts.js

@@ -0,0 +1,58 @@
+/**
+ * The intent-first hand-off — how a prompt typed on the public site reaches the platform.
+ *
+ * A visitor types the idea for a project on the marketing site before they have an account. The
+ * site cannot write into the platform's browser storage (IndexedDB is per origin) and must not put
+ * the prompt in a URL, so the prompt takes a short detour through the platform's own cache: the
+ * site stashes it behind an unguessable reference, sends the browser to the platform with only that
+ * reference, and the platform picks the prompt up once — after which it lives in the visitor's own
+ * browser until they decide what to do with it.
+ *
+ * Everything here is serializable and runtime-free: the site, the manager API and the manager web
+ * read the same declarations, and none of them may reinvent a name the others parse.
+ */
+/** Every address of the hand-off. API routes are guest routes; the landing is a screen. */
+export const intent = Object.freeze({
+    base: 'viable:manager-api:intent:base',
+    stash: 'viable:manager-api:intent:stash',
+    pickup: 'viable:manager-api:intent:pickup',
+    landing: 'viable:manager-web:intent:landing',
+});
+/** Where the guest API lives, and the screen the visitor's browser is sent to. */
+export const INTENT_API_PATH = '/public/intent';
+export const INTENT_LANDING_PATH = '/start';
+/** The flow the two sides walk. */
+export const INTENT_FLOW = 'viable:intent';
+/**
+ * How long the platform keeps a stashed prompt waiting for pickup. Short on purpose: the pickup
+ * happens the moment the browser lands, so anything older was abandoned, and a prompt is personal
+ * data the platform has no business holding once nobody is coming for it.
+ */
+export const INTENT_TTL_SECONDS = 120;
+/** The longest prompt the platform will create a project from (`PromptSchema` in viable). */
+export const INTENT_PROMPT_MAX = 8192;
+/**
+ * The reference's shape: `createIdOfLength(24)` — Base58, so no `0`, `O`, `I` or `l`. Anything else
+ * is refused before the cache is asked, which keeps a crafted reference from ever being a key.
+ */
+export const INTENT_REF_LENGTH = 24;
+export const INTENT_REF_PATTERN = '^[1-9A-HJ-NP-Za-km-z]{24}$';
+/** The flow payload key carrying the reference — short, because a payload is CSV-joined. */
+export const INTENT_PAYLOAD_REF = 'ref';
+/** How long the visitor's draft survives in their own browser waiting for a decision. */
+export const INTENT_DRAFT_TTL_MS = 24 * 60 * 60 * 1000;
+/** How long a suspended landing waits while the visitor signs in or registers. */
+export const INTENT_SUSPEND_TTL_MS = 30 * 60 * 1000;
+/** Steps of {@link intentFlow}, exported so a screen never spells one as a literal. */
+export var IntentFlowStep;
+(function (IntentFlowStep) {
+    /** The public site: the prompt is typed and stashed. */
+    IntentFlowStep["Compose"] = "compose";
+    /** The platform's landing screen: the stash is picked up. */
+    IntentFlowStep["Land"] = "land";
+    /** The platform's own sign-in dispatcher. */
+    IntentFlowStep["SignIn"] = "sign-in";
+    /** The platform's home screen, where the draft is offered back. */
+    IntentFlowStep["Review"] = "review";
+})(IntentFlowStep || (IntentFlowStep = {}));
+//# sourceMappingURL=consts.js.map

package/build/intent/consts.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"consts.js","sourceRoot":"","sources":["../../src/intent/consts.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,2FAA2F;AAC3F,MAAM,CAAC,MAAM,MAAM,GAAG,MAAM,CAAC,MAAM,CAAC;IAClC,IAAI,EAAE,gCAAgC;IACtC,KAAK,EAAE,iCAAiC;IACxC,MAAM,EAAE,kCAAkC;IAC1C,OAAO,EAAE,mCAAmC;CACpC,CAAC,CAAA;AAEX,kFAAkF;AAClF,MAAM,CAAC,MAAM,eAAe,GAAG,gBAAgB,CAAA;AAC/C,MAAM,CAAC,MAAM,mBAAmB,GAAG,QAAQ,CAAA;AAE3C,mCAAmC;AACnC,MAAM,CAAC,MAAM,WAAW,GAAG,eAAe,CAAA;AAE1C;;;;GAIG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,GAAG,CAAA;AAErC,6FAA6F;AAC7F,MAAM,CAAC,MAAM,iBAAiB,GAAG,IAAI,CAAA;AAErC;;;GAGG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG,EAAE,CAAA;AACnC,MAAM,CAAC,MAAM,kBAAkB,GAAG,4BAA4B,CAAA;AAE9D,4FAA4F;AAC5F,MAAM,CAAC,MAAM,kBAAkB,GAAG,KAAK,CAAA;AAEvC,yFAAyF;AACzF,MAAM,CAAC,MAAM,mBAAmB,GAAG,EAAE,GAAG,EAAE,GAAG,EAAE,GAAG,IAAI,CAAA;AAEtD,kFAAkF;AAClF,MAAM,CAAC,MAAM,qBAAqB,GAAG,EAAE,GAAG,EAAE,GAAG,IAAI,CAAA;AAEnD,uFAAuF;AACvF,MAAM,CAAN,IAAY,cASX;AATD,WAAY,cAAc;IACxB,wDAAwD;IACxD,qCAAmB,CAAA;IACnB,6DAA6D;IAC7D,+BAAa,CAAA;IACb,6CAA6C;IAC7C,oCAAkB,CAAA;IAClB,mEAAmE;IACnE,mCAAiB,CAAA;AACnB,CAAC,EATW,cAAc,KAAd,cAAc,QASzB"}

package/build/intent/entrypoints.d.ts

@@ -0,0 +1,27 @@
+import type { IntentPickupBody, IntentPickupResult, IntentProtocolOptions, IntentStashBody, IntentStashResult } from './types.js';
+/**
+ * Declare the intent-first hand-off: two GUEST API routes and the landing screen's address.
+ *
+ * No guard and no gate anywhere on the API — the caller is a visitor who has no account yet — and
+ * no `service` on any route: each consumer fills it in (the public site names the platform's
+ * services in its own configuration; the manager binds them to its own).
+ *
+ * TODO(cors): these routes ride the framework's global `origin: '*'` CORS policy (no credentials).
+ * If viable ever restricts allowed origins globally, this entrypoint must keep answering the public
+ * site's origins — owlmeans.com, owlmeans.pl and, in dev/stage, `http://localhost:4321`.
+ *
+ * The landing screen is `sticky`, like the OAuth consent screens: it is an ordinary in-app screen
+ * that a visitor arrives at directly from another origin.
+ */
+export declare const makeIntentProtocols: (opts?: IntentProtocolOptions) => {
+    base: import("@owlmeans/entrypoint").EntrypointProtocol<import("@owlmeans/entrypoint").OpenRequest, import("@owlmeans/entrypoint").OpenValue>;
+    stash: import("@owlmeans/entrypoint").EntrypointProtocol<{
+        body: IntentStashBody;
+    }, IntentStashResult>;
+    pickup: import("@owlmeans/entrypoint").EntrypointProtocol<{
+        body: IntentPickupBody;
+    }, IntentPickupResult>;
+    landing: import("@owlmeans/entrypoint").EntrypointProtocol<import("@owlmeans/entrypoint").OpenRequest, import("@owlmeans/entrypoint").OpenValue>;
+};
+export type IntentProtocols = ReturnType<typeof makeIntentProtocols>;
+//# sourceMappingURL=entrypoints.d.ts.map

package/build/intent/entrypoints.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"entrypoints.d.ts","sourceRoot":"","sources":["../../src/intent/entrypoints.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EACV,gBAAgB,EAAE,kBAAkB,EAAE,qBAAqB,EAAE,eAAe,EAAE,iBAAiB,EAChG,MAAM,YAAY,CAAA;AAEnB;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,mBAAmB,UAAU,qBAAqB;;;;;;;;;CAkB9D,CAAA;AAED,MAAM,MAAM,eAAe,GAAG,UAAU,CAAC,OAAO,mBAAmB,CAAC,CAAA"}