Skip to content
NORA
Roadmap

What has shipped, what is building, and what is next.

We publish roadmap honestly and keep it current with the actual state of the work. Status labels are not aspirational — they reflect what exists today.

Current quarter

15 items

Critical-path tasks. Each one unblocks the next end-to-end round trip — sign up, ingest, ask, verify.

  1. PLAT/DB-01in-progress
    Provision Neon Postgres (get DATABASE_URL)
    PLAT
  2. PLAT/DB-02in-progress
    Run initial migration (`prisma migrate deploy`)
    PLAT
  3. PLAT/DB-03in-progress
    Enable `pgvector` + `pgcrypto` extensions
    PLAT
  4. PLAT/AUTH-01in-progress
    Wire `clerkMiddleware()` in `src/proxy.ts`
    PLAT
  5. PLAT/AUTH-02in-progress
    Clerk webhook to provision `User` + default `Archive`
    PLAT
  6. PLAT/AUTH-03in-progress
    `resolveArchiveContext` reads Clerk `auth()` instead of cookies
    PLAT
  7. PLAT/DEPLOY-01in-progress
    `vercel.json` with function limits + headers
    PLAT
  8. PLAT/DEPLOY-02in-progress
    Document all env vars; set in Vercel dashboard
    PLAT
  9. PLAT/DEPLOY-03in-progress
    Map domains (norafoundation.io → marketing, app.norafoundation.io → workspace)
    PLAT
  10. PLAT/OBS-01in-progress
    Sentry error tracking
    PLAT
  11. PLAT/TEST-01in-progress
    Install Vitest
    PLAT
  12. PLAT/TEST-08in-progress
    Typecheck in CI
    PLAT
  13. PLAT/DEPLOY-07in-progress
    GitHub Actions CI/CD
    PLAT
  14. DATA-002in-progress
    Generate `prisma/migrations/` history (not just schema file)
    DATA
  15. DATA-017in-progress
    Publish real (non-ephemeral) Ed25519 public key at `/.well-known/meridian-key.pem`
    DATA

Next quarter

21 items

P0 work staged behind the critical path. Sequenced so we never ship a UI surface ahead of the data and security primitives it depends on.

  1. DATA-001planned
    Prisma generate in CI
    DATA
  2. DATA-003planned
    pgvector wired
    DATA
  3. DATA-004planned
    Embedding pipeline
    DATA
  4. DATA-005planned
    FTS tsvector + GIN index
    DATA
  5. DATA-006planned
    Enrichment write path
    DATA
  6. DATA-007planned
    Person/Alias write path
    DATA
  7. DATA-019planned
    Production blob backend (Vercel Blob / S3)
    DATA
  8. DATA-020planned
    Proper HTML parser (not regex)
    DATA
  9. AI-01planned
    Session owner check (hijack vector)
    AI
  10. AI-02planned
    Archive scoping on sessionId
    AI
  11. AI-05planned
    Real quota check vs Stripe tier
    AI
  12. AI-21planned
    archive_search tenant isolation audit
    AI
  13. UI-01planned
    Clerk login wire
    UI
  14. UI-02planned
    Clerk signup wire
    UI
  15. UI-11planned
    Markdown rendering in chat
    UI
  16. UI-22planned
    Ingest progress real (not fake states)
    UI
  17. PLAT/SEC-01planned
    Rate limiting on /api/*
    PLAT
  18. PLAT/SEC-02planned
    Body-size limits on ingest
    PLAT
  19. PLAT/BILL-01planned
    Subscription model + Stripe checkout
    PLAT
  20. PLAT/EMAIL-01planned
    Welcome email pipeline (Resend)
    PLAT
  21. PLAT/LEGAL-01planned
    /legal/terms + /legal/privacy
    PLAT

Horizon

18 items

P1 work — required before public launch but not blocking the first round trip. Order is heuristic, not committed.

  1. DATA-021planned
    SearchHit enum safety
    DATA
  2. DATA-022planned
    Chunk positions populated
    DATA
  3. DATA-029planned
    Real refutation challenges (not placeholder declined)
    DATA
  4. DATA-030planned
    Enrichment / Search / Brief templates
    DATA
  5. AI-09planned
    Remove hardcoded "pro" fallback in router
    AI
  6. AI-30planned
    Deep research as real agent loop (not just prompt)
    AI
  7. AI-32planned
    /api/chat rate limiting
    AI
  8. UI-04planned
    Clerk user-created webhook
    UI
  9. UI-12planned
    Code-block syntax highlighting in chat
    UI
  10. UI-23planned
    Gmail / Dropbox / iCloud connector cards
    UI
  11. UI-30planned
    Billing tier from DB (not hardcoded)
    UI
  12. UI-44planned
    loading.tsx per route
    UI
  13. UI-50planned
    Mobile sidebar
    UI
  14. PLAT/AUTH-05planned
    Password reset
    PLAT
  15. PLAT/SEC-07planned
    KMS key rotation policy
    PLAT
  16. PLAT/OBS-02planned
    Structured logging across modules
    PLAT
  17. PLAT/PERF-03planned
    Bundle audit + treeshake budget
    PLAT
  18. PLAT/DOCS-03planned
    ARCHITECTURE.md ratified
    PLAT

Completed

3 items

Shipped artifacts. Each carries a Canon attestation hash you can match against the source repository — placeholder hashes today; signed once the live signer is wired.

  1. CANON-V0.1.0done
    Canon v0.1.0 draft-rfc published (CC0)
    Specification, JSON schema, and CC0 licence published. github.com/NORA-BITSY/nora-canon.
    CANON
  2. FOUNDATION-INITdone
    NORA Foundation public site live
    Marketing surface, mandate, drift ledger, and reference brand system shipped.
    PLAT
  3. MERIDIAN-BETAdone
    Meridian private beta workspace
    Chat, archive, ingest, attestation, and Canon stages wired against the reference schema.
    UI

Generated 2026-04-19 from BACKLOG.md · 214 atomic tasks tracked (75 P0, 111 P1, 28 P2).

How the roadmap works.

Shipped means the artifact is publicly accessible and verifiable by anyone. For the specification, this means the CANON.md and JSON schema are published under CC0 on GitHub. For implementation phases, it means executable code has been run against the reference corpus.

In progress means active work with committed timeline. We do not mark items in-progress unless code or spec changes are being committed in the relevant repository.

Next means the work is designed and sequenced, with dependencies understood. Timeline estimates are honest best guesses, not commitments.

Future means the direction is clear but the path is not fully designed. These items are included for ecosystem planning purposes, not as near-term promises.

The roadmap is updated in source at github.com/NORA-BITSY. If you see a discrepancy between what this page says and what is in the repository, the repository is correct — and please let us know.

The roadmap needs support to stay on schedule.

Specification drafting, implementation work, verifier tooling, and adversarial review all have resource requirements. Donor and partner support determines the pace.

Support the foundation →Contribute to the work