Switchboard.
Use whenOne active AI run needs an owner, context, approvals, and a next move in one place.
DecisionContinue, review, fix, or resume the run.
SF-WEB-11 / Portfolio Map
Run. Review. Replay. Improve.
Make consequential AI work owned, reviewable, replayable, and improvable.
Start from the state of the work: a live run, a software change, a saved failure, or the deeper system around them.
Find Your Front Door ->
Compare The Front Doors ->
Built for teams that need ownership, review, replay, and improvement in consequential AI work.
Choose A Front Door
Start from what is happening.
Use the state of the work to choose an entry point. The deeper system comes after the front door is clear.
Signal Box.
Use whenOne AI-assisted software change needs structured review before it moves forward.
DecisionReady, risky, blocked, or needs another pass.
Test Stand.
Use whenA saved failure needs to be rerun as a comparable scenario.
DecisionFixed, still failing, or changed in a meaningful way.
System map.
Use whenThe front door is clear and you need supporting records, packages, extensions, or patterns.
DecisionWhat future runs should inherit, change, or avoid.
How It Fits
How the products fit together.
The portfolio spans four connected states: run live work, review decisions, replay failures, and improve the system.
Run
Run live work.
Switchboard keeps active runs, owners, approvals, and next moves in one place. Admin Socket handles the narrower administrative lanes around that work.
Review
Review and release with confidence.
Signal Box, Interlock, and Repo Pinion make change review, conflict checks, and release posture easier to see.
Replay
Replay what failed.
Test Stand reruns saved failure scenarios so teams can compare outcomes and see what changed.
Improve
Improve the next run.
Engine House, Record Office, Toolroom, Packhouse, Agentic Trunkline, and research work carry better records, packages, extensions, and patterns forward.
Front Doors
Compare the front doors.
Most teams do not need the whole portfolio on day one. They need the clearest entry point for the work in front of them.
Switchboardreview one AI run and choose the next move
Live Work- Use this whenOne run of consequential AI work needs a visible owner, visible context, and a visible next move.
- ForEngineering and workflow leads managing consequential AI work.
- What it doesKeeps one line of work, its runs, approvals, artifacts, and costs together.
- Why start hereIt is the clearest entry point when work is already in motion.
Signal Boxreview one code change before it moves forward
Change Review- Use this whenOne AI-assisted code change needs structured review before anyone decides whether it is safe to move.
- ForEngineering leads and senior reviewers handling review-heavy change work.
- What it doesTurns a change into a single review surface with context and a decision.
- Why start hereIt shortens the path from “what changed?” to “what should we do next?”
Test Standreplay one saved failure and compare outcomes
Failure Replay- Use this whenOne saved workflow failure needs to be rerun as a comparable scenario before you trust a result.
- ForWorkflow owners, evaluators, and release reviewers investigating recurring failures.
- What it doesReplays saved failure scenarios so teams can compare outcomes and see what changed.
- Why start hereIt helps teams improve by showing whether a fix worked or a failure pattern is still present.
Deeper Layers
The rest of the system.
Once the front door is clear, these layers show how the broader system is administered, reviewed, extended, and packaged.
Operational layers
These adjacent working surfaces help teams manage review, runtime, coordination, and release operations.
Admin Socket
Administrative workflows and system status for operational teams.
Lane Capsule
Repo Pinion
Repo state and release posture for teams preparing work for review.
Repo Review
Interlock
Coordination surface for overlapping work, ownership, and closeout.
Route Board
Engine House
Runtime control for local model inventory, health, and lifecycle actions.
Provider Bay
Shared foundations
These foundations keep records, extensions, packages, and reusable patterns consistent across the portfolio.
Record Office
Shared record structure for work that spans products.
Record Frame
Toolroom
Extension framework for testing and issuing plugins.
Plugin Manifest
Packhouse
Packaging and receipt layer for reusable operating packages.
Package Preview
Agentic Trunkline
Shared library for carrying proven patterns into downstream systems.
Reference Library
Research and benchmark work support the system, but the clearest place to start is the front door that matches the state of the work.
Next Step
Choose the front door for the work in front of you.
If the work is already moving, start with Switchboard. If a software change needs structured review, start with Signal Box. If a failure needs to be replayed, start with Test Stand.