Strengthen Company Brain V0 implementation plan - #19
Open
jackye426 wants to merge 13 commits into
Open
Conversation
Dream-phase work (lint, backlinks, extract, synthesize, patterns, embed, orphans) was never scheduled — it only ran when someone invoked `gbrain dream` by hand. gbrain ships an autopilot daemon for exactly this, but `autopilot --install` only targets launchd/systemd/cron, so on Windows pm2 has to be the supervisor. Autopilot's cycle already covers sync and embed, so keeping those in the 3-minute loop only contended for the same locks. The loop is reduced to the one step autopilot cannot do: committing collector output, since gbrain indexes commits rather than the working tree. Moves the loop out of the gitignored .cortex/ so the ecosystem entry points at a tracked file, and retires gbrain-embed-drain.mjs now that embedding is the daemon's job. Co-authored-by: Cursor <cursoragent@cursor.com>
The README still described Railway vault + twin-pipeline as the daily path, so agents (and Jack) could not tell what was actually running. Rewrite it as the live collect → commit → autopilot contract, including manual backfill/compilers and local MCP wiring. Also persist the Windows autopilot launcher (--inline, windowsHide) so detached gbrain.exe children stop opening a terminal per job. Co-authored-by: Cursor <cursoragent@cursor.com>
Call mingw git.exe from the commit loop, and give autopilot a hidden console so Bun-spawned git inherits it instead of popping a window. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: jackye426 <jackye426@users.noreply.github.com>
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Co-authored-by: jackye426 <jackye426@users.noreply.github.com>
jackye426
marked this pull request as ready for review
August 26, 2026 14:39
Co-authored-by: jackye426 <jackye426@users.noreply.github.com>
Isolated Forma company-state service with fail-closed COMPANY_BRAIN_* config, founder approval, and a signed GitHub webhook path. Personal Cortex credentials and records are refused. Co-authored-by: jackye426 <jackye426@users.noreply.github.com>
Co-authored-by: jackye426 <jackye426@users.noreply.github.com>
Co-authored-by: jackye426 <jackye426@users.noreply.github.com>
Reuse the existing Cortex EU project with cb_* tables; add migration and GitHub App manifest scripts; document the live provisioning runbook. Co-authored-by: jackye426 <jackye426@users.noreply.github.com>
Reads existing Cortex Supabase credentials and generates bearer tokens for local Company Brain provisioning. Co-authored-by: Cursor <cursoragent@cursor.com>
Add railpack/railway config, PORT binding for Railway, and env sync script. Live at cortexcompany-brain-production.up.railway.app. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
COMPANY_BRAIN_*config, production persistence requirement, strong unique secretsHow to verify
Fresh and legacy-upgrade migrations execute in in-memory Postgres tests, including RLS, atomic ingestion, replay recovery, and verdict behavior.
Not in this slice: Granola, Codex collector, Gmail, Notion, live GitHub App install, or provisioning the dedicated Supabase project.