· ENPT-BR
Grok Build for Alembic · Evidence & selection

Reconnaissance: map before you import

See Grok Build as several surfaces—not one blob—then locate the single gap Alembic should own.

Primary source
Pinned Grok Build README

Pinned upstream commit: b189869b7755d2b482969acf6c92da3ecfeffd36

The Simple layer stands alone; open Technical for exact contracts and edge cases.
You will be able to
  • Name the upstream surfaces without collapsing them into “the CLI”.
  • Locate Alembic's existing owners for runtime, tools, workspaces, and UI.
  • Defend the provider seam as the smallest useful adoption.
1

The big idea

Grok Build combines a terminal UI, a headless scripting mode, an ACP editor surface, an agent runtime, tools, workspace management, and persistent sessions. Alembic already owns most of those jobs. The useful move is not to port the product; it is to connect the released CLI through Factory's narrow provider seam.

Think of it like… Treat the upstream repository like a complete airport. Alembic does not need a second runway, tower, and baggage system; it needs one standards-compliant gate where an arriving Grok flight can dock. The analogy breaks because software ownership is enforced by interfaces and tests, not concrete and signage.

The pinned README names four principal Rust crates: pager/TUI, shell runtime and entry points, tools, and workspace/checkpoints. It also documents three consumption surfaces: TUI, headless, and ACP. This decomposition is the unit of analysis; each surface gets its own overlap verdict.

First-party upstream code is Apache-2.0, while the repository separately identifies vendored ports and notices. Alembic's phase-one TypeScript adapter is clean-room against observable CLI contracts; it copies no Rust and creates no second runtime owner.

Evidence: Pinned Grok Build README

TUIheadlessACPpagershell Safe: one adapter owns command + event translation.
See Grok Build as several surfaces—not one blob—then locate the single gap Alembic should own.
2

Compare the boundaries

Safe
Safe: one adapter owns command + event translation.
Risky
Risky: copy Rust runtime, tools, and session engine into Alembic.
SurfaceUpstreamAlembicVerdict
TUI / cockpitFull-screen terminal productTUI, web, cockpit already existALREADY
Agent runtime / toolsRust loop plus built-in toolsHarness, VM, Factory, adaptersALREADY
Headless CLI protocolStable external process boundaryMissing first-class Grok providerADOPT

First-party upstream code is Apache-2.0, while the repository separately identifies vendored ports and notices. Alembic's phase-one TypeScript adapter is clean-room against observable CLI contracts; it copies no Rust and creates no second runtime owner.

3

Real code and commands

/tmp/alembic-grok-build-20260716 @ b189869…
git -C /tmp/alembic-grok-build-20260716 rev-parse HEAD
# b189869b7755d2b482969acf6c92da3ecfeffd36

rg -n "Repository layout|Headless|ACP|License" \
  /tmp/alembic-grok-build-20260716/README.md
How to reach it
sed -n '1,150p' /tmp/alembic-grok-build-20260716/README.md

Evidence: RESOURCES.md

4

Visual atlas

inputproofTUI
Trace the boundary: TUI.
surfaceseamownerheadless
Locate the owner: headless.
claimwithout gateevidenceat boundaryvsACP
Compare claim and evidence: ACP.
learnexecuteverifypager
Read the sequence: pager.
complete?yes / noshell
Find the decision gate: shell.
inputprooftools
Trace the boundary: tools.
surfaceseamownerworkspace
Locate the owner: workspace.
claimwithout gateevidenceat boundaryvssessions
Compare claim and evidence: sessions.
learnexecuteverifyhooks
Read the sequence: hooks.
complete?yes / noplugins
Find the decision gate: plugins.
inputproofsandbox
Trace the boundary: sandbox.
surfaceseamownerworktrees
Locate the owner: worktrees.
claimwithout gateevidenceat boundaryvsFactory
Compare claim and evidence: Factory.
learnexecuteverifyAgentProvider
Read the sequence: AgentProvider.
5

Practice and feedback

Predict before revealing

If Alembic already owns orchestration and tools, which upstream surface has the lowest overlap?

The headless process protocol: it connects a real agent without importing its internals.

Retrieval cards

Retrieval cardsPagerClick or press Enter to flip
PagerThe full-screen TUI surface.
Retrieval cardsShellClick or press Enter to flip
ShellRuntime plus headless/stdio entry points.
Retrieval cardsProvider seamClick or press Enter to flip
Provider seamFactory's command/event translation boundary.
Retrieval cardsClean-roomClick or press Enter to flip
Clean-roomImplement documented behavior without copying Rust.
Grok Build combines a terminal UI, a headless scripting mode, an ACP editor surface, an agent runtime, tools, workspace management, and persistent sessions. Alembic already owns most of those jobs. The useful move is not to port the product; it is to connect the released CLI through Factory's narrow provider seam.
The pinned README names four principal Rust crates: pager/TUI, shell runtime and entry points, tools, and workspace/checkpoints. It also documents three consumption surfaces: TUI, headless, and ACP. This decomposition is the unit of analysis; each surface gets its own overlap verdict.

Explore the upstream surface

Choose a surface and read the ownership verdict.

Verdict

Four-slide summary

Pager

The full-screen TUI surface.

Shell

Runtime plus headless/stdio entry points.

Provider seam

Factory's command/event translation boundary.

Clean-room

Implement documented behavior without copying Rust.

Check your model

Spaced review

What is the phase-one adoption unit?

The provider fills a verified seam. Runtime and TUI already have Alembic owners.
6

Sources and next move

Pinned Grok Build READMEb189869b7755 · readmePinned headless mode guideb189869b7755 · headlessPinned session management guideb189869b7755 · sessionsRESOURCES.mdGrok Build for Alembic
Ask your teacher to challenge a verdict, replay an event, or review a future unit against the same proof discipline.