Operating Flow — AG Run Pad Hub

Notion / Tilog Plans

Source of Truth

Tilog (Notion AI) reads the AG Run Pad and crafts a bounded executor prompt. The prompt defines: goal, workspace, allowed files, forbidden files, approved commands, MCP policy, acceptance criteria, and the output report contract.

Notion / Tilog Output

Current Active Run: Slice 3
Workspace: d:\TRILONG-tools\ag-run-pad-landing

Files Allowed:
  ✔ src/pages/distilled-lessons.astro
  ✔ src/pages/operating-flow.astro
  ✔ src/pages/index.astro

Commands Approved:
  ✔ npm run build

Files Forbidden:
  ✗ .env, *.key, *.pem, secrets
  ✗ Files outside workspace

Human Gate

Long Approves

The human (Long) reads the prompt in Notion, reviews the scope, approves or adjusts it, then copy-pastes it to Antigravity. No code changes happen before this gate. This is the control point that prevents unintended side effects.

Human Gate Checklist

Before pasting to Antigravity:

  [ ] Workspace path is correct
  [ ] Allowed files list is scoped correctly
  [ ] Forbidden files are explicit
  [ ] Commands are bounded (one command only)
  [ ] MCP policy is stated
  [ ] Output contract is specified
  [ ] Acceptance criteria is clear

Antigravity Executes

Bounded Local Execution

Antigravity confirms the workspace path, then executes within the approved boundary. It creates or edits only the listed files, runs only the approved commands, and reports any failures immediately instead of auto-fixing.

Antigravity Execution Log

WORKSPACE CHECK
  Confirmed: d:\TRILONG-tools\ag-run-pad-landing ✔

FILES CREATED
  + src/pages/distilled-lessons.astro
  + src/pages/operating-flow.astro

FILES MODIFIED
  ~ src/pages/index.astro (nav links updated)

COMMAND RUN
  > npm run build
  ✔ Build completed in 612ms

Output Sync

Report Appended to AG Run Pad

Antigravity uses the gated Notion MCP to append the full executor report to the AG Run Pad Output Inbox. The status row in the Active Run table is updated. No other pages are created or modified.

Notion MCP Update

TARGET PAGE
  🧪 AG Run Pad (7bdd75a9...)

UPDATES SENT
  ✔ Section 1: Status → "Slice 3 complete"
  ✔ Section 4: Latest Run ID → AG-RUN-2026-05-20-005
  ✔ Section 13: Full Slice 3 executor report appended

MCP POLICY RESPECTED
  ✗ No new pages created
  ✗ No unrelated pages touched
  ✗ No secrets read

Tilog Reviews

Notion AI Verification

Tilog reads the new output in the AG Run Pad inbox, checks scope compliance, build status, security boundaries, and visual summary. It then writes a review verdict and optionally drafts the next approval prompt.

Tilog Review Verdicts

Review Checklist:
  ✔ PASS — All acceptance criteria met
  ✔ PASS WITH WARNINGS — Minor issues flagged
  ✗ NEEDS FIX — Prompt Long with fix plan
  ✗ BLOCKED — Execution was stopped early
  ✗ REJECT / ROLLBACK — Changes must be undone

Current Review: PASS
  → Workspace confirmed
  → Build passed
  → No secrets, no deploy, no git
  → Notion MCP gated correctly

Archive & Close

Lesson Gets Distilled

After Long confirms the review, learnings from the run are distilled into the skill/handoff pages. The AG Run Pad is kept lean — only the current active run context stays. The cycle resets for the next slice.

Distillation Output

ARCHIVED TO
  → AG-08 · Run Pad Workflow

LESSON ADDED
  Title: Workspace path gate
  Rule: Always confirm workspace before command.

SKILL PAGE UPDATED
  + Rule #3: One command per approval
  + Process: Bounded executor with output contract

RUN PAD STATUS
  → Active run context cleared
  → Ready for next slice or project

View Lessons →

The Operating Flow

Source of Truth