# ANIDASO Internal Knowledge Portal — Phase Plan

## Current source of truth

GitHub repository: `Acolatse-Apps/anidaso-portal`

The project has been migrated from the local folder `C:\Users\kwame\Desktop\anidaso-portal` and connected to the Vercel project `anidaso-portal` under `Neowec's projects`.

Vercel is the deployment layer. GitHub is the source of truth.

## Operating rule

Use connected tools first. Ask Benedictus for manual PowerShell only when a connector cannot complete the action, when local bulk generation is required, or when a browser-only authorization step is needed.

## Phase 1 — Control and audit

Create project control documents, inventory the current book files, identify which files are website pages, HTML books, PDFs, mobile editions, source documents, tools, and Supabase files.

Deliverables:
- `ANIDASO_PHASE_PLAN.md`
- `BOOK_RECONSTRUCTION_STANDARD.md`
- `BOOK_INVENTORY.md`
- `WEBSITE_HTML_PDF_SEPARATION_RULES.md`

## Phase 2 — Library reconstruction

Upgrade the premium library into a real institutional publication hub. The library should not merely list files. It should guide readers through categories, summaries, HTML reader links, PDF publication links, and status indicators.

Core requirements:
- global publication search
- category filters
- HTML book links
- PDF publication links
- book purpose summaries
- status labels

## Phase 3 — Governance book reconstruction

Use the Governance, Institutional Leadership & Founder Continuity Framework as the first reconstruction test. The current version is only a starting point. It is not the final design or language standard.

Create three separate outputs:
1. Website summary page
2. HTML interactive reader
3. Formal PDF publication

## Phase 4 — Search architecture

Strengthen search at two levels:
- global search across the publication library
- per-book search inside each HTML book

Search should cover title, category, keywords, section headings, chapter titles, and selected excerpts.

## Phase 5 — Book-by-book publication program

After the Governance book is approved as the standard, apply the same structure to every book in the library.

Each book must receive:
- summary website page
- refined HTML reader
- formal PDF publication
- metadata and search indexing

## Phase 6 — Supabase verification

Supabase must be verified from repository config before being treated as the source of data. Do not create a new Supabase project unless Benedictus explicitly approves it.

Inspect:
- `assets/supabase-config.js`
- `assets/supabase-client.js`
- `supabase/migrations/`
- `supabase/seed/`

## Phase 7 — Deployment verification

Every meaningful batch must be pushed to GitHub. Vercel should redeploy automatically. After each deployment, verify status through Vercel tools and inspect logs if needed.

## Completion definition

The portal is complete only when:
- GitHub is current
- Vercel deployment is ready
- premium library works
- global search works
- per-book search works
- HTML books are readable and navigable
- PDF publications look like formal official books
- language has been rewritten away from generic AI style
- all book links and downloads work