Project Registry

The project registry is the future-ready list of projects shown in the Situation Room.

Current Schema

board.config/projects.json contains:

{
  "projects": [
    {
      "id": "foryoutune",
      "displayName": "ForYouTune",
      "phase": 1,
      "status": "active",
      "repo": "sur00108/foryoutune-dev",
      "readTokenSecret": "DEV_REPO_READ_TOKEN",
      "startedAt": null,
      "progressPercent": 85,
      "primaryLinks": {
        "currentState": "/generated/status/current-state/",
        "tasks": "/generated/tasks/",
        "timeline": "/generated/timeline/build-timeline/",
        "history": "/history/overview/",
        "harness": "/harness/overview/"
      },
      "notes": "Current Phase 1 source project. Existing generated docs remain in their current paths."
    }
  ]
}

Registration Model

Phase 2, Phase 3, and future SaaS projects should later be added as additional objects in the projects array.

Current Limitation

The registry is used for the UI skeleton only. It does not drive sync behavior yet.

Future Sync Boundary

Actual multi-repo sync belongs to BOARD001F. It should start only when real Phase 2 repo/data exists.

Secret Rule

readTokenSecret must contain only the GitHub Secret name. Never place a real token or secret value in the registry.

Phase 2 / Phase 3 Registration Checklist

1. Add a new project object to board.config/projects.json.
2. Add the required GitHub read token secret if the repo is private.
3. Confirm source repo read-only access.
4. Run the board build.
5. Start BOARD001F only when real repo/data exists.
6. Verify that existing generated/history/harness pages remain untouched.