ACTION REQUIRED CARDS
Project: ASTRA: KALYUG PROTOCOL Date: 2026-08-01 Rule applied: Never assume. Never invent project information. If information is missing, create Action Required cards.
These are the questions I refused to answer for you. Each is information that does not exist in any supplied document, where guessing would have silently created a fact the project would then be built on. Each card carries a recommendation — but the decision is yours.
These cards are designed to be the seed data for ProjectOS. On first boot the dashboard should show them as the project's real backlog.
Blocking ProjectOS (needed before I write any code)
AR-001 — Deployment hostname
Ref: C-08, I-06 · Priority: CRITICAL
Missing: Confirmation of where ProjectOS is deployed.
Verified 2026-08-01: invert.aurionglobal.my/ → HTTP 302 (live). /legacy/ → HTTP 200 (live). The 5th Element / Samudra pilot is serving from this hostname now.
Recommendation: astra.aurionglobal.my, new Caddy block, Invert/Samudra untouched.
If you insist on invert.: I will first relocate Samudra to its own hostname and preserve /legacy/, then deploy ASTRA at the root. That is more work and more risk, and it must be an explicit instruction.
AR-002 — Database and stack
Ref: C-09, I-14 · Priority: CRITICAL
Missing: Whether to introduce hosted Supabase or use the existing Contabo Postgres.
Recommendation: existing Postgres, dedicated astra schema and role, Prisma, Next.js/TS/Tailwind/shadcn, containerised behind aifh_caddy. Keeps "single source of truth" true, adds no vendor.
AR-003 — Authentication model
Priority: HIGH
Missing: Who can access ProjectOS. Single-user? Named accounts? Public read-only pages? Anything that touches contractors later needs roles now.
Recommendation: single-owner login now, but a users/roles table from day one so adding an artist or contractor later is a row, not a migration.
AR-004 — Archiving the trading project
Priority: HIGH Missing: What "archive it, keep it accessible" means concretely. ASTRA's ProjectOS and the trading systems are unrelated domains; an "Archived Projects" section inside a game-development tool is an odd coupling. Recommendation: ProjectOS is ASTRA-only. Archiving = leaving Samudra/Invert running on their own hostname with a link from the Aurion estate map. If you instead want ProjectOS to be a general Aurion project OS with ASTRA as its first project, say so — that is a materially larger and different build, and I would want to scope it separately.
Blocking the game design (do not block ProjectOS)
AR-005 — Progression model
Ref: C-01, I-01 · Priority: CRITICAL Missing: Are relics and runes in-match only, or account-persistent? Recommendation: in-match only. Account progression = cosmetics and titles, zero stats. Consequence of the alternative: hard rules #6, #7 and #11 must be formally amended.
AR-006 — Players per match
Ref: C-04, I-02 · Priority: CRITICAL Missing: The number. Nothing downstream is estimable without it. Note: decide this before confirming netcode, and price dedicated servers at that count before confirming the number.
AR-007 — Netcode and hosting topology
Ref: C-04, I-02 · Priority: CRITICAL Missing: Whether hosting is server-authoritative on dedicated servers, and whether Unity Netcode for GameObjects is actually the chosen stack. Concern: NGO's client-hosted/relay topology conflicts with the "Fair gameplay" pillar and with low-end Android hosts. Realistic alternatives: UGS Game Server Hosting with an authoritative server, Netcode for Entities, or Photon Fusion/Quantum.
AR-008 — Anti-cheat
Ref: C-04, R-02 · Priority: CRITICAL Missing: Any anti-cheat plan at all. "Fair gameplay" is currently an unsupported claim on a platform where APK tampering is trivial.
AR-009 — Prana
Ref: C-03, I-03 · Priority: CRITICAL Missing: The entire system. It is a stated project pillar that appears in no design document.
AR-010 — Cultural design policy
Ref: R-01, I-04 · Priority: CRITICAL Missing: Policy on depicting and monetising Hindu deities; specifically Sita as a combatant, and cosmetic sales for Hanuman and Krishna. Recommendation: written policy plus a named external reviewer with sign-off at each character gate, before any character art is commissioned.
AR-011 — Performance budget
Ref: C-05, I-05 · Priority: CRITICAL Missing: Target worst-case device, triangle/draw-call/texture-memory ceilings, per-asset budgets, thermal policy, download-size ceiling. Note: the ProjectOS Asset Manager cannot function without this. It is the highest-value missing document after Prana.
AR-012 — The 10 combat zones
Priority: HIGH Missing: All ten. The GDD says "10 Combat Zones" and names none. The Map Builder module has nothing to display.
AR-013 — The 10 weapon families
Priority: HIGH Missing: All ten, plus the evolution model, relic interaction and catalyst mechanic named in the ProjectOS brief but absent from the GDD.
AR-014 — Hero abilities
Priority: HIGH Missing: Every ability, cooldown and impact value for all five heroes. Character Manager has five names and nothing else.
AR-015 — Barrier system
Priority: HIGH Missing: Definition. Listed in the GDD and in the ProjectOS asset taxonomy; specified nowhere.
AR-016 — Karma
Ref: C-14, I-16 · Priority: MEDIUM Missing: Definition. Recommendation: behavioural only, zero combat and zero loot effect.
AR-017 — Core combat numbers
Ref: R-05 · Priority: HIGH Missing: Match length, TTK, circle/shrink rules, map size, inventory model, healing, Duo revives, damage model, recoil, aim-assist policy.
AR-018 — Team, budget and schedule
Ref: R-03 · Priority: HIGH Missing: All of it. The Production Bible has four phase names, no dates, no headcount, no budget, no gates. Note: with 5 heroes + 10 weapon families + 10 zones, a conservative estimate is 2,000–4,000 unique assets. That number should be confirmed or the scope cut before Phase 1.
AR-019 — Meta loop and seasons
Ref: C-13, I-17 · Priority: MEDIUM Missing: The retention loop that Rule #8 requires, the season structure that the Milestone Tracker expects, and the post-launch phase the Production Bible omits.
AR-020 — Backend, store and telemetry
Ref: R-02, I-13 · Priority: HIGH Missing: Accounts, entitlements, IAP validation, cosmetics store, matchmaking, telemetry. For a cosmetics-only title this is the revenue system.
Summary
20 Action Required cards. 10 CRITICAL. 4 block ProjectOS (AR-001 to AR-004) — I need these answered to start building. 16 block the game, not the tool — and every one of them can be answered inside ProjectOS once it exists. That is the strongest argument for building the tool first, and it is why I think your instinct on sequencing is right.