Portfolio/Internal system
Vector Core
Lightweight portal, due November 8, 2026
Give Vector Labs institutional memory and organizational awareness across all ventures.
The operating record for the organization. Not a separate venture, and not a fourth product competing for nights and weekends.
The tree
.-. .-. FRUIT What good looks like .-( '-' )-. Better decisions, less administrative .' '. thrash, and an organization that can say ( ( ) ( ) ) what it is neglecting. '._ _.' '~---------~' | * * | * * LEAVES What weekly use looks like . . | . . Priorities, experiments, decisions, costs, `. .' | `. .' and a short note on where attention went. `-..-' | `-..-' .--. | .--. BRANCHES Modules .-' `-. | .-' `-. Portfolio, goals, decisions, knowledge, ( )------|------( ) and operations first. Projects, a full `-. .-' | `-. .-' risk system, and the agent wait. `--' | `--' | TRUNK The application and its data model | Every venture-specific record belongs to a | venture. Caldera's compliance work must | never be stored as if it were Eligibl's. .----|----. ROOTS Tools already in use .-' | `-. GitHub, Cursor, Neon, Cloudflare, GoDaddy, .' | `. Excel, and the knowledge already ____/__________|__________\____ accumulated. Add a tool only when one of ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SOIL Why an internal system is justified
SoilWhy an internal system is justified
No separate points on this layer.
RootsTools already in use
No separate points on this layer.
TrunkThe application and its data model
No separate points on this layer.
BranchesModules
No separate points on this layer.
LeavesWhat weekly use looks like
No separate points on this layer.
FruitWhat good looks like
No separate points on this layer.
The next year
Vector Core is useful enough to run the week from
Keep the internal portal lightweight and in use
Improve decision records, knowledge, and reporting
Introduce organization-aware AI only if the records are trustworthy
November 2026 through October 2027. Bars are the November 1 timeframes, read onto this year. August through October are open on purpose. The blueprint does not schedule them. October 2026 is already behind this chart. A dim bar is not started. A full bar is in motion or done. Blocked work drops to a thin opacity so it stays visible.
Objectives
The year chart above is the same work, drawn from November 2026 through October 2027. Status stays in this browser.
Vector Core/By November 8, 2026
Vector Core is useful enough to run the week from
Dashboard, venture profiles, trees, quarterly objectives, decisions, the knowledge base, and a place for costs. Mark this done when you have used it, not when the screens exist.
Vector Core/Q4 2026
Keep the internal portal lightweight and in use
Build the record. Then stop building and run the portfolio from it.
Vector Core/Q1 2027
Improve decision records, knowledge, and reporting
Vector Core/Q2 2027
Introduce organization-aware AI only if the records are trustworthy
The useful question is: look across all three businesses. What am I neglecting, where is the risk, and what should next week be?
November 8 checklist
0 of 7
Mark a line when you have used it on a real week. The screens existing is not the milestone.
What this build holds
The November 1 plan was to rework the existing Vector Core repository, keep its API and news writer, and put Neon underneath the organizational records. That repository was not in this workspace, so those pieces have not been migrated. This portal is the organizational layer. Edits stay in this browser until a database is connected.
Portfolio
See every venture, its stage, and what it is for.
In this build
Goals
Track quarterly objectives and the next 30 days.
In this build
Decisions
Record what was decided, why, the alternatives, and when to review it.
In this build
Knowledge
Hold the tree, the product descriptions, and the questions still open.
In this build
Operations
Track time, costs, vendors, and infrastructure without pretending to be the books.
Started
Projects
A year chart for each venture, from the objectives already on the record.
In this build
Risk register
Vendors, infrastructure, compliance, and cross-venture dependencies.
Not a system yet
Organization-aware agent
Read each venture at a chosen level of detail, and draft Eligibl copy from the record rather than from invented memory.
Started
Left out on purpose
- A complicated task manager, or a private copy of Jira, Notion, or Excel.
- Multi-agent orchestration.
- Automated bookkeeping before the numbers are real.
- An integration with every service Vector Labs touches.
- Weeks spent perfecting the interface.
- An agent that invents facts the record does not contain.