EPISTEMIK DEVELOPMENT NOTE Internal request workflow — 25 August 2026 Prepared 13 October 2026 from archived development artifacts. WHAT WAS BUILT Office Snack Requests is a small internal workflow application. Employees submit requests; an office manager approves or declines them. Accepted product decisions include oldest-first review, employee visibility of decline reasons, and explicit limits on request fields. THE OPERATOR DECISION The requirements were accepted with changes on 19 August 2026. An additional manager sign-out failure story required a clear explanation, preservation of the session and review data, and no false return to a signed-out state. This was an amendment before the delivery described here, not a recorded post-delivery conversation with a nontechnical customer. WHAT THE SYSTEM DID The development pipeline produced backend and interface artifacts. A verification step identified a missing session-cookie SameSite attribute. The remediation path patched it, and the application was re-served and checked again. Maintainers also fixed platform issues and restarted parts of the run. RECORDED RESULT The result highlighted on the landing (US-012): invalid whitespace-only input was blocked locally without creating a request. The employee corrected it without losing their note. The application created one request (HTTP 201), with the supplied note and a visible Open status. Desktop and mobile report entries record this sequence. An additional recorded result (US-011): a failed employee sign-out preserved the active session and displayed a retry action. A successful retry then ended the session and returned to sign-in. Desktop and mobile entries record this behavior; the mobile retry entry records HTTP 204. The archived report also lists 43 passing units across 28 story identifiers. However, its US-028 entries describe failed manager login, whereas the operator amendment labels manager sign-out failure as US-028. This semantic mismatch was identified during preparation of this note. Consequently, the aggregate count is not presented as evidence that every accepted requirement was correctly covered. The report requires reconciliation before such a coverage claim can be made. IMAGE The accompanying image is an unaltered archived screenshot of the generated employee request form. It depicts the application produced in the experiment, not Epistemik's future user interface. Its empty fields contain no user data. Original archive reference: story-sweep-2-3 / us-017-requests-new-employee-office-snack-requests-test.png. Application candidate revision: a766f8df1384cd359d685bcfa90d3d7e53d363a3. Run reference: snack-requests-9-rail. BOUNDARIES - Local development experiment; no cloud or public deployment in this run. - Technical maintainer corrections, restarts, and rebaselining were necessary. - This does not establish zero developer intervention, universal reliability, customer acceptance, measured productivity gains, or a publicly available product. - The screenshot is illustrative; a screenshot alone does not prove behavior. - No fresh execution was performed for this public note. RELATED DEVELOPMENT: REQUIREMENT CHANGES A separate Kiln Share experiment on 11–12 October 2026 propagated a stricter sign-out requirement through backend and interface changes. Initially its changed behavior remained unproven. Experiment EXP-251 subsequently recorded that story (US-015) as passed: a browser check forced a server error on sign-out and judged the resulting error state. A later correction pass retained this story's earlier verdict. The application's aggregate was still 28 passed, 8 failed, and 4 unproven. That experiment also required a maintainer-authored structured change request and manual recovery steps. It is evidence of a requirement-change mechanism in development, not yet a demonstration that a nontechnical user can complete the whole experience without engineering help. Its counts must not be combined with the separate Office Snack Requests result above. PROVENANCE This note summarizes the operator decision, delivery journal, conformance ledger, and browser proof matrix for snack-requests-9-rail. The related development note uses EXP-249, EXP-251, EXP-254, EXP-255 and Kiln Share's declared browser proof. Epistemik remains in development. Public access is not yet available.