Historical local qualification: Source 7cf4b26e focused Core 22/22 and Dashboard 26/26 checks passed. The historical bounded local record keeps their exact scope. Historical source 7cf4b26e passed the 3,286/3,286 full checks and all 36 installed families. Independent bounded local evidence acceptance passed; exact-final-head CI is recorded separately from this frozen local proof. Module-specific and broader limits remain below.
Additive profiles: Verified local snapshot. Historical receipts retain their recorded scope; live qualification and customer delivery require separate evidence. The two snapshots qualify their original sources; combined-source review and exact-final-head CI remain required.
The private package serves the built Dashboard over loopback with a caller-owned typed backend. It requires Node.js 26.8.1 or later and has no runtime npm dependencies. The browser assets, React runtime and licence notices are included. Importing the module does not listen, open storage, load assets or call the backend.
import { startDashboard, type DashboardBackend } from 'software-factory/dashboard';
import { DASHBOARD_PROTOCOL } from 'software-factory/dashboard-contract';
// Implement the named synchronous read methods and optional typed commands.
declare const backend: DashboardBackend;
const server = await startDashboard({ backend, assets: { kind: 'packaged' }, port: 0 });
console.log(server.url, DASHBOARD_PROTOCOL);
// Close stops serving; it does not cancel a caller's running effect.
await server.close();
Backend ownership
The backend owns Product membership, durable state, isolation, replay and command clocks. Reads are synchronous and passive. They return typed DTO payloads without transport envelopes. The selected server profile adds /3 or /4 explicitly; domain payload semantics remain unchanged. A read must refuse an absent Product; a returned Product identity must match the request. The server owns the protocol, clock and period window, token, limits and effective capabilities. It validates HTTP and Guidance input before any standalone command callback. It has no Portfolio, Git, journal or provider dependency. It is a trusted in-process interface, not a sandbox for untrusted code.
Supply commands.saveGuidance only when the backend durably deduplicates the same command ID and exact request, refuses stale expected revisions, retains immutable revisions and isolates Products. The server adds direct-entry provenance after the shared grammar validates the request. A lost acknowledgement is retried with the same ID and unchanged content. Return a recorded result or throw DashboardBackendError with the closed failure kind. Messages in typed failures are public, bounded text; never put secrets in them. Unexpected exceptions produce a fixed generic error. No callback receives an HTTP request or response.
Bounded inspection and uncertain effects
For positively identified transient store contention, a backend may throw DashboardBackendError({kind:'journal-contention'}). The server responds with fixed 503 JOURNAL_UNAVAILABLE text and Retry-After: 1 for GET/HEAD only; HEAD remains empty. The backend must establish contention from validated storage facts, rather than matching message text. Use journal-storage, journal-missing-or-schema or journal-refused for other journal failures; these carry no retry hint. Commands never receive this read hint, and it does not authorise a retry or replace an original command ID. Callers cannot supply HTTP headers or a delay in the failure value.
An inspection capability has a captured commission: { scopeId, waitMs } and run(request). waitMs is an integer from 1 to 60,000. The stable scope identifies the caller's shared exclusion domain across Products, servers and restarts. Before any effect, the backend must durably admit the supplied operation ID against that scope. It must refuse a missing, unreadable or unresolved ledger, reconcile a deadline or interrupted invocation, and never treat expiry as permission to retry. The server's per-instance BUSY fence cannot provide cross-process durability.
The request contains Product ID, operation ID, scope ID and a real UTC deadline. Only a durably verified completed result or not-started refusal is terminal. An unresolved result, rejection, malformed result or mismatched Product leaves the local fence set. The HTTP wait ends with 503 when the deadline expires; the original promise remains observed. A late terminal result can release the local fence but cannot replace the response. A late rejection stays fenced and cannot leak its exception. Another Product on that server is also BUSY. Do not block JavaScript execution; the server cannot pre-empt trusted caller code.
Closing stops new requests and pending HTTP waiters; it does not cancel effects or erase caller ledger state. Restart only with the same stable scope and a backend that checks durable admission. Reconciliation belongs to the caller; there is no generic server store, automatic retry, browser reset or reconciliation endpoint. An unresolved local fence remains until a late terminal result, or close followed by caller-owned durable reconciliation and a new server. Lost durable state refuses further dispatch.
Built assets and boundaries
assets: { kind: 'packaged' } reads the included build. Alternatively, { kind: 'directory', directory } takes an absolute canonical directory holding the same complete manifest format. Startup captures and verifies every resource before listening: hashes, sizes, inventory, local dependency references, protocol and brand resources. Missing, stale, partial or linked trees fail closed. No development source or API-only fallback is offered. The manifest records the browser source commit, source hashes, pinned build tool versions and output hashes; it is provenance, not a signature or authority to trust a third party's code. Choose a trusted build directory.
GET and HEAD only read facts. Commands require the server's loopback Host, same Origin, same-origin fetch policy, JSON, bounded bodies and its per-process token. This is a local interface for a trusted caller and local user, not remote authentication. Command switches can disable supplied capabilities; requesting an absent capability refuses startup. The Factory's existing journal adapter keeps its original command order, replay and API-only option; it remains a separate source consumer.
See the package export index for the public entry points and other modules. Local synthetic and installed-consumer proofs are not a production or customer adoption claim.
Optional milestone owner interface. initial source slice
DashboardOptions.milestones accepts an explicitly qualified DashboardMilestoneBackend. Omitting it preserves the existing session capabilities and commands. The initial source UI records a name/objective and optional achievement guidance, with zero criteria and a separate "Set next" action. Research, tickets and overall resource forecasts remain unavailable. The separately supplied real-Core binding and passive reviewed-plan endpoint passed independent source review. Built-browser checks cover save/select/reload and narrow screens. Historical source 7cf4b26e passed the 3,286/3,286 full checks and all 36 installed families. Independent bounded local evidence acceptance passed; exact-final-head CI is recorded separately from this frozen local proof.
The caller supplies an already commissioned retention scope and synchronous read, prepare and execute methods. Before invocation, prepare durably retains the exact expanded original M01 request; execute receives only its opaque envelope ID. Same-ID drift conflicts, and an unresolved original excludes replacement after client/server restart. read returns the retained pending identity or an attributable final outcome. Missing records never establish non-commit. No default store, key, actor, grant, policy, allowance or core instance is created. Constructor capture calls no method.
Every call must check current READ and applicable mutation authority under the qualified common physical fence; exact historical replay may use READ alone. All registry, values, policy and authority writers must join that fence. This is a caller qualification obligation, not a guarantee established by a scope string. If the milestone host omits saveGuidance, Guidance edits are disabled; neither the standalone backend's legacy writer nor the source Factory writer is a fallback.
New routes below /api/products/:id/milestones use the existing transport guards and a factory-milestone-ui/1 result envelope. GET reads; guarded POST /prepare takes a bounded request ID/version and closed owner action; POST /execute takes only the opaque envelope ID. No actor or source/authority pins come from the browser. Native Promise data never grants authority; malformed or exceptional mutation acknowledgements remain unknown. Results and errors contain no private host diagnostics. The initial source checks use synthetic caller retention and establish HTTP/UI-state behaviour only. Real M01 composition, two qualified arrangements, responsive browser proof, new built assets and independent package review remain required.
Caller-owned Dashboard presentation
startDashboardV4({...options, presentation}) requires {protocol: 'sf-dashboard-presentation/1', journalLabel}. The nonempty plain-text label has the same 80-character/320-byte bound as digest presentation; controls and malformed Unicode refuse before assets load or backend calls. /api/session carries the captured label under factory-dashboard/4. The browser uses it for the navigation name and document title, and journal failures use it with the same fixed statuses and retry rules. All read, mutation, error, milestone and delayed inspection envelopes use the selected version. This label does not rename domain states or grant backend authority.
The real browser build's factory-dashboard-assets/2 manifest declares exactly the ordered compatible pair [/3, /4]. A legacy /1 asset manifest supports only /3 and refuses /4 startup; no inferred compatibility or fallback exists. The client validates the finite pair and requires the /4 presentation. startDashboard retains /3, Factory branding and its original session shape. Caller text is escaped; a /4 session omits the Factory brand plate.
