lookout

Fleet 26%51/199 tasks · 14/45 phases

github.com/coding-octopus-llc/atlas72%atlas · phase 132 plansupdated 43s agohelm →

Atlas — 33/35 (94%)

Phase 1 · Setup — 2/2 · complete

1.1 /atlas:setup — config owner, artifacts root, verification gates complete
1.2 Configure this repo via /atlas:setup complete

Phase 2 · Spec — 2/2 · complete

2.1 /atlas:spec — the spec transformer, plus shipped template complete
2.2 Retroactive spec for the spec skill complete

Phase 3 · Brief — 1/1 · complete

3.1 /atlas:brief — the lifecycle head, plus shipped template complete

Phase 4 · Research — 2/2 · complete

4.1 Spec for the research skill (clean-room from the ADRs) complete
4.2 /atlas:research — the investigation transformer, plus shipped template complete

Phase 5 · Plan — 2/2 · complete

5.1 Spec for the plan skill complete
5.2 /atlas:plan — the breakdown transformer, plus plan and phase templates complete

Phase 6 · Breakdown — 1/1 · complete

6.1 /atlas:breakdown — flesh out one plan phase complete

Phase 7 · Base helm — 2/2 · complete

7.1 Helm data layer — parse ADRs, specs, plans, and designs complete
7.2 Base views — log4brains-style decision browser, specs, designs, plans complete

Phase 8 · Design — 1/1 · complete

8.1 /atlas:design — spec to design doc, plus shipped template complete

Phase 9 · Decide — 1/1 · complete

9.1 /atlas:decide — MADR decision records complete

Phase 10 · Build assistance — 4/4 · complete

10.1 /atlas:scaffold — skeleton, test stubs, work file at depth: scaffold complete
10.2 /atlas:implement — scope resolution, depth menu, confirm plan complete
10.3 /atlas:implement — ladder execution and the obligation ledger complete
10.4 setup: [implement] confirm-plan toggle complete

Phase 11 · Capture loop — 4/4 · complete

11.1 /atlas:mark — one developer-completed piece complete
11.2 /atlas:log — capture an issue with relevance-matched context complete
11.3 /atlas:diagnose — investigate, propose, never apply complete
11.4 setup: [logs] error-log locations complete

Phase 12 · Reconciliation — 4/4 · complete

12.1 The task-level finish command complete
12.2 /atlas:survey — the project-wide sweep complete
12.3 /atlas:survey — staged confirmations and the improvement loop complete
12.4 setup: [ticketing] section complete

Phase 13 · Helm completion — 7/8 · in-progress

13.1 Drift view and attached drift display complete
13.2 Briefs and research views complete
13.3 Ticket coverage and graceful no-ticketing degradation complete
13.4 Prompt generation complete
13.5 setup: [helm] per-repo settings complete
13.6 Ticket enrichment at generate time complete
13.7 Ticket chip: native status color and assignee planned
13.8 Artifact type identity on tabs and cross-references complete

Phase 14 · Finalize command name — 0/1 · planned

14.1 Land the finish command's final name; sweep the interim references planned

Helm generator as a hardened, consumable library — 0/11 (0%)

Phase 1 · Injectable, side-effect-free core — 0/2 · planned

1.1 Introduce Ctx and thread repoRoot/opts through build() and every reader planned
1.2 Add the warnings[] return channel and inject(data, opts?) signature planned

Phase 2 · Confined, bounded reads — 0/3 · planned

2.1 Route all reads through readFileBounded/listDirBounded with repoRoot confinement planned
2.2 Enforce three deterministic caps via a shared budget planned
2.3 Make build() total — degradations become warnings, never throws planned

Phase 3 · Template injection fixes — 0/2 · planned

3.1 Escape the JSON splice and the project name in inject() planned
3.2 Escape quotes in the client-side esc() planned

Phase 4 · Full artifact surface — 0/2 · planned

4.1 Add readLog for .atlas/log/ entries planned
4.2 Add readWorklog for .atlas/worklog/ work files planned

Phase 5 · Packaging as a pinnable library — 0/2 · planned

5.1 Add the root package.json with files allowlist and exports map planned
5.2 Sync package.json version to the release tag planned

github.com/coding-octopus-llc/lookout58%fleet-status-board · phase 32 plansupdated 43s agohelm →

fleet status board — 15/18 (83%)

Phase 1 · Fleet pipeline — 6/6 · planned

1.1 Package scaffold: pnpm project, hono + TOML parser deps, atlas pinned by tag complete
1.2 Config loader: roster + token table, resolution by longest host+owner match, rejection rules complete
1.3 Platform adapters for GitHub and GitLab (remoteUrl, validate, verifyReadOnly, blobUrl, commitUrl) complete
1.4 Fetcher: fresh shallow sparse clone, two-phase checkout, per-project timeout, temp cleanup complete
1.5 Parser adapter: pinned build(), exposing the plan→phase→task tree with statuses and counts complete
1.6 Snapshot store: per-project last-good results on disk complete

Phase 2 · Aggregate progress model — 2/2 · planned

2.1 Per-project completion roll-up, active position, attention counts complete
2.2 Fleet summary, health list, progress ordering, stale carry-forward (retire buckets) complete

Phase 3 · Board and serving — 5/6 · planned

3.1 Scheduler: interval cycles, coalesced manual trigger, no overlap complete
3.2 Hono server: board page, helm pages, /api/aggregate, /api/refresh, /api/health complete
3.3 SSE hub and live client (in-place re-render, reconnect indicator) in-progress
3.4 Progress renderer: fleet strip, roster rows, lookout-health line complete
3.5 In-place drill-to-task and helm/forge deep-links complete
3.6 Helm page regeneration via inject and deep links complete

Phase 4 · Image and deploy — 2/4 · planned

4.1 Container image: Node + git, writable temp, lookout serve entrypoint complete
4.2 Deploy the image and wire token secrets into the container environment planned
4.3 Onboard the full fleet roster and shake out per-project errors planned
4.4 Ops notes: deploy steps and roster-change restart complete

multi-branch aggregation — 0/8 (0%)

Phase 1 · Branch discovery — 0/2 · planned

1.1 Adapter: listOpenMrBranches for GitHub (PRs) and GitLab (MRs), read-only planned
1.2 Branch planner: integration + open-MR branches, deduped, degrade on MR-API failure planned

Phase 2 · Multi-branch fetch and aggregate — 0/4 · planned

2.1 Per-branch fetch fan-out over the existing fetcher, concurrency-capped planned
2.2 Filter atlas-less open-MR branches via the sparse clone (no new permission) planned
2.3 Snapshot store keyed per (project, branch) for per-branch carry-forward planned
2.4 Aggregator fold: integration baseline + in-flight open-MR branches, canonicality rule planned

Phase 3 · Presentation — 0/2 · planned

3.1 Board: one row per project (F13) with an in-flight indicator for open-MR work planned
3.2 Helm route + links keyed by (project, branch) planned

gitlab.com/terrainone/infra5%terrainone-infra · phase 11 planupdated 43s agohelm →

TerrainOne Web Services Infrastructure — 3/58 (5%)

Phase 1 · Standalone Application Delivery — 3/22 · planned

1.6 Deploy Admin panel via GitLab pipelines complete
1.7 On-demand deploy of any admin branch to dev in-progress
1.8 Create Site Dockerfile (Astro SSR) in-progress
1.9 Create Site Docker Bake definition in-progress
1.10 Create Site Docker Compose (Astro SSR) in-progress
1.11 Build and push Site to the GitLab Container Registry in-progress
1.12 Deploy Site from the GitLab Container Registry in-progress
1.13 On-demand deploy of any site branch to dev in-progress
1.14 Build and push reap-astro to GHCR complete
1.15 Deploy reap-astro from GHCR in-progress
1.16 Build and push reap-hono to GHCR complete
1.17 Deploy reap-hono from GHCR in-progress
1.18 Rework reap compose networks and remove its Traefik planned
1.19 Build and push supersonic-bot to GHCR in-progress
1.20 Deploy supersonic-bot from GHCR planned
1.21 Create React Native mobile app CI/CD pipeline planned
1.22 Implement semantic-release for Site planned
1.23 Publish Site images at the release version and pin prod deploys to it planned
1.24 Implement semantic-release for Admin planned
1.25 Publish Admin images at the release version and pin prod deploys to it planned
1.26 Pin reap production deploys to the semantic-release version planned
1.27 Switch supersonic deploys to trigger variables and pin prod to semver planned

Phase 2 · Terraform Infrastructure — 0/8 · planned

2.1 Initialize Terraform shared module and provider configuration planned
2.2 Create per-environment root modules with isolated backends planned
2.3 Create compute resources and minimal cloud-init in the platform module planned
2.4 Configure networking, firewall and DNS in the platform module planned
2.5 Create the managed database module, instantiated in prod only planned
2.6 Configure module and root outputs planned
2.7 Deploy and verify the dev environment planned
2.8 Provision state buckets, locking and credential hygiene planned

Phase 3 · Ansible Configuration — 0/8 · planned

3.1 Set up Ansible foundation and dynamic inventory planned
3.2 Configure group variables and vault secrets planned
3.3 Create environment templates for the three services planned
3.4 Create the bootstrap playbook planned
3.5 Create the deployment role structure planned
3.6 Create service-specific playbooks planned
3.7 Create the PostgreSQL initialization script planned
3.8 Test the full Ansible deployment end to end planned

Phase 4 · Docker Configuration — 0/6 · planned

4.1 Create the infrastructure Docker Compose template planned
4.2 Create the Traefik configuration template planned
4.3 Create the Admin Docker Compose template planned
4.4 Create the API Docker Compose template planned
4.5 Create the Site Docker Compose template planned
4.6 Verify all Docker templates render and compose cleanly planned

Phase 5 · CI/CD Pipeline — 0/5 · planned

5.1 Create the infra CI/CD pipeline skeleton planned
5.2 Create Terraform plan and apply jobs planned
5.3 Create deploy jobs planned
5.4 Configure GitLab CI/CD variables planned
5.5 Test the CI/CD pipeline end to end planned

Phase 6 · Monitoring Stack — 0/9 · planned

6.1 Create the monitoring Docker Compose template planned
6.2 Configure Prometheus planned
6.3 Create Prometheus alert rules planned
6.4 Configure Loki and Promtail planned
6.5 Configure Grafana planned
6.6 Configure Alertmanager planned
6.7 Create the monitoring Ansible playbook planned
6.8 Add monitoring DNS records planned
6.9 Deploy and verify the monitoring stack planned

github.com/coding-octopus-llc/reap-astro0%—0 plansupdated 43s agohelm →

no plans

github.com/coding-octopus-llc/reap-hono0%—0 plansupdated 43s agohelm →

no plans

github.com/coding-octopus-llc/supersonic-bot0%laracord-framework-port · phase 11 planupdated 43s agohelm →

Laracord framework port — 0/17 (0%)

Phase 1 · Scaffold Laracord and the verification harness — 0/4 · planned

1.1 Merge a Laracord scaffold into the repo root planned
1.2 Quarantine legacy code from Laracord discovery planned
1.3 Stand up PHPUnit planned
1.4 Add the tokenless discovery check planned

Phase 2 · Port the Werewolf game — 0/3 · planned

2.1 Decouple RoleManager from the framework planned
2.2 Wire WerewolfService and game services into Laracord's container planned
2.3 Green the game test suite under the new harness planned

Phase 3 · Port commands and message events — 0/5 · planned

3.1 Port the status command planned
3.2 Port say, spike, and prototype commands planned
3.3 Port the werewolf command planned
3.4 Port the sonic trigger and the seven live MessageListener behaviors as Events planned
3.5 Record the TwoTruthsAndALie disposition planned

Phase 4 · Cut over and verify — 0/5 · planned

4.1 Delete the legacy framework and glue planned
4.2 Remove the phase-1 quarantine planned
4.3 Run the full tokenless acceptance sweep planned
4.4 Update the run/setup docs planned
4.5 Live acceptance in a test guild planned

github.com/terrainone-pty-ltd/app0%—0 plansupdated 43s agohelm →

no plans

gitlab.com/terrainone/admin0%—0 plansupdated 43s agohelm →

no plans

gitlab.com/terrainone/api0%migrate-off-firebase · phase 11 planupdated 43s agohelm →

Migrate off Firebase to the Laravel API — 0/9 (0%)

Phase 1 · Firebase ID token authentication guard — 0/4 · planned

1.1 Add Firebase Admin SDK dependency and per-environment configuration planned
1.2 Implement the token-verification guard and protected-route wiring planned
1.3 Implement uniform 401 JSON rejection for all invalid-token cases planned
1.4 Write Pest feature tests covering the spec's acceptance criteria planned

Phase 2 · Attractions read endpoints (Firestore-backed) — 0/5 · planned

2.1 Set up Firestore access (Admin SDK Firestore component + gRPC) planned
2.2 Build the attraction normalizer to the documented read model planned
2.3 Build the list endpoint (versioned route, guard-protected, ordered by name) planned
2.4 Build the detail endpoint with 404 handling planned
2.5 Write Pest feature tests covering the spec's acceptance criteria planned

gitlab.com/terrainone/site0%adopt-payloadcms · phase 11 planupdated 43s agohelm →

Adopt PayloadCMS — 0/43 (0%)

Phase 1 · Monorepo restructure — 0/6 · planned

1.1 Move the Astro app to apps/web and namespace it @terrainone/web planned
1.2 Declare the workspace members in pnpm-workspace.yaml planned
1.3 Keep commitlint and its config at the workspace root planned
1.4 Rewrite the atlas gates as workspace-aware commands planned
1.5 Re-path the Docker build context and GitLab pipeline for apps/web planned
1.6 Confirm the site is unchanged after the move planned

Phase 2 · CMS app and database — 0/6 · planned

2.1 Scaffold apps/cms as a Payload 3 Next.js app planned
2.2 Pin Payload, Next and React at the workspace root planned
2.3 Configure the Postgres adapter and a local database planned
2.4 Export the Payload config and generated types from @terrainone/cms planned
2.5 Establish the migration workflow planned
2.6 Seed a first admin user planned

Phase 3 · Content model and media — 0/7 · planned

3.1 Model the Media collection with upload sizes planned
3.2 Model about, contact and pricing from the existing data modules planned
3.3 Model the homepage planned
3.4 Model the shared site content the pages render planned
3.5 Model testimonials as a collection planned
3.6 Enable drafts and versions on the page content planned
3.7 Set access control so only authenticated editors can write planned

Phase 4 · Admin authentication — 0/5 · planned

4.1 Install and wire payload-oauth2 with the Google provider planned
4.2 Implement the domain-or-address allowlist planned
4.3 Unit-test the allowlist rule planned
4.4 Add the Continue with Google button to the admin login view planned
4.5 Disable the local email/password strategy planned

Phase 5 · Site integration and content migration — 0/8 · planned

5.1 Depend on @terrainone/cms and read content through the Local API planned
5.2 Switch the four pages to SSR planned
5.3 Serve uploaded media independently of the CMS app planned
5.4 Render about, contact and pricing from CMS content planned
5.5 Render the homepage from CMS content planned
5.6 Render shared header/footer/app-link content from the globals planned
5.7 Migrate today's content into the CMS planned
5.8 Make the e2e suite work against SSR pages planned

Phase 6 · Preview — 0/4 · planned

6.1 Add a preview route that renders draft content planned
6.2 Configure admin.preview on the page collections planned
6.3 Subscribe to Payload's save event and refresh the preview planned
6.4 Verify preview on all four pages planned

Phase 7 · Deployment and CI — 0/7 · planned

7.1 Build the CMS image and add it to the bake targets planned
7.2 Add Postgres and the uploads volume to the deployed stack planned
7.3 Run migrations in the deploy flow planned
7.4 Raise CI and host Node to Payload's floor planned
7.5 Provide Postgres to CI for the e2e suite planned
7.6 Wire the environment and secrets planned
7.7 Verify content and media survive a redeploy planned