1.5 KiB
1.5 KiB
OSVauco / OPAX – TODO
Managed by PLAN thread. Update when phases move between sections. Last updated: 2026-05-22
NOW
- Phase 3 — verify GEMINI.md Nemotron loop and boot script
NESTE OPPGAVEdisplay. - Confirm Cloud Run
opax-mcp-coreis back online after crash andcurl https://opax.vauco.no/pingreturns200 OK. - Re-verify domain mapping
opax.vauco.no→ghs.googlehosted.comstill active after Cloud Run redeploy.
NEXT
- Phase 4 — Docs hardening: update
LEARNINGS.md,SECRETS-SETUP.md,IAP-SETUP.mdwith current state. - Phase 5 — Medioteq staging: deploy
medioteq-oss-coreto Medioteq GCP project → mapmedioteq-oss.vauco.no→ Google OAuth. - Phase 5b — Medioteq prod: deploy
medioteq-os-core→ mapmedioteq-os.vauco.no→ BankID prep. - Create
docs/MEDIOTEQ-IAM-CONTRACT.mdanddocs/MEDIOTEQ-GOVERNANCE-WHITEPAPER.md. - Add cross-project status endpoint in OPAX so hub can query Medioteq project status without touching clinical data.
LATER
- IAP on
opax.vauco.no(restrict to@vauco.noonly). - BankID on
medioteq-os.vauco.no. - Multi-client onboard pattern:
<client>-oss-core→<client>-os-corewith IAM contract template. opax-mcp/restructured as proper module subtree.- Full boot cycle acceptance test (automated).
BLOCKED
- Cloud Run
opax-mcp-corecrashed — must redeploy before Phase 3 verification can complete. (2026-05-22)