0019 — Responsive contract for institutional surfaces

• Date: 2026-09-18
• State: accepted
• Authority: Codex 1 Art. III; Codex 0 §§11, 20–21; Codex 6; STD-X §§3.7–3.9; STD-Q §§5, 12
• System / owner: SYS-12 Infrastructure / DIV-05 Technology

Decision

Every human-facing Anabasis surface uses one responsive implementation from a 320px phone through tablet and desktop widths. Shared chrome and controls carry a 44px minimum touch target. Wide records remain tables where space supports comparison; on phones the administrator lead desk presents the same authorized data and actions as records with expandable detail. Lesson pages place the lesson before the course index on phones. No parallel mobile site, permission path, or content source is created.

Why

Access from a phone or tablet is part of the institution's service, not a secondary presentation. The former shared footer produced page overflow at tablet width, compact controls fell below the touch standard, and desktop-first workspace patterns obscured primary work on phones. Shared corrections reduce divergence as surfaces grow.

Nine-field record

1. 1Decision: adopt the responsive contract above across registered surfaces.
2. 2Authority: Technology owns implementation; surface-owning divisions retain content and outcome authority.
3. 3Purpose: increase access, education, trust, and durable institutional capability.
4. 4Scope: presentation and interaction geometry only; no doctrine, content, data model, or permission change.
5. 5Evidence: 140 reachable public routes rendered at 390px with zero page overflow, missing h1, HTTP failure, or browser error; 60 representative checks passed at 320×568, 390×844, 768×1024, 1024×768, and 1440×900; signed-in Scholar surfaces passed at 320px; anonymous Scholar, Faculty, and Admin entry redirected to enrolment; a permitted PDF attachment returned 200 and displayed Attached.
6. 6Risk: compact editorial links may remain visually quiet while their effective hit area increases; monitor wrapped labels as content grows.
7. 7Alternatives: a global overflow clamp and a separate mobile site were rejected because they conceal defects and create divergence.
8. 8Review date: 2027-03-18; owner DIV-05 Technology.
9. 9Result: accepted on 2026-09-18. Public and Scholar evidence passed. The available learner account was correctly denied administrative data and had no governed Faculty course, so role-authorized mutation paths remain covered by existing server-side policy rather than falsely claimed as exercised here.

Institutional Critic

1. 1100× scale: shared primitives and route-family patterns prevent per-page mobile forks.
2. 2Assumptions: 320px–1440px covers the supported width contract; physical-device browser chrome remains a periodic review item.
3. 3Simpler solution: fixing shared sources is simpler than page-level overflow suppression.
4. 4Duplication: no new surface, route, system, or content source.
5. 5Enterprise view: dense operational work remains comparative on tablet/desktop and actionable on phone.
6. 6First-time view: primary actions and navigation remain reachable without horizontal page gestures.
7. 7Legal, operational, security: permissions are unchanged and enforced server-side; anonymous denial was reverified.
8. 8Debt: administrator and faculty role-authorized mutations were not exercised because no such test role was available; DIV-05 must rerun them when a governed test account exists, by 2026-10-18.
9. 9Doctrine: the change advances capability, access, trust, and longevity without altering institutional doctrine.

Codex 8 evaluation

• Revenue potential: indirect, through practical access to existing pathways.
• Implementation cost: moderate presentation and verification work.
• Maintenance cost: reduced through shared responsive patterns.
• Operational complexity: unchanged permissions and workflows; lower device-support burden.
• Customer value: high for visitors, applicants, Scholars, Faculty, and operators using touch devices.
• Enterprise value: high for field and tablet use of institutional workflows.
• Long-term strategic value: high; one durable surface system serves future devices and content growth.

Rollback

Revert Decision 0019's presentation changes as one set if a verified desktop workflow regresses. Do not retain a global overflow clamp or a parallel phone-only implementation.