Founder's Desk / Coding Team

Coding Team

The Coding Team treats GitHub's remote repository state — not this or any other ephemeral sandbox — as the durable source of truth. Most of this page is read-only status. The one write-capable control is the explicit, human-gated "Approve and Apply" step in the Coding Request panel below — nothing else on this page can modify GitHub.

Runtime Diagnostic (temporary)

Safe troubleshooting information only. The token value itself is never shown.

GitHub token configured
No
GitHub token non-empty
No
Token has surrounding whitespace
No
Repository access
Authentication failed
GitHub HTTP status
(none)
Branch HEAD read
Failed
GitHub diagnostic category
API error
GitHub message
(none)
Rate limit
(none)
Rate limit remaining
(none)
Rate limit reset
(none)
Retry after
(none)

Diagnostic

FOUNDERS_DESK_GITHUB_TOKEN is not set at runtime — no GitHub request was attempted.

Claude Connection

Safe connectivity check only. The API key value itself is never shown.

Anthropic API key configured
No
Anthropic API key non-empty
No
Claude connection
Failed
Model
(none)
HTTP status
(none)

Diagnostic

ANTHROPIC_API_KEY is not set at runtime — no Anthropic request was attempted.

Repository Inspection

Demonstration question: "Read the repository tree, inspect app/desk/coding/page.tsx, and summarize what this page currently does." Runs only when you click the button below — nothing here calls Anthropic automatically.

Governed Coding Request

Describe a change and Claude will inspect the repository, then prepare a governed Change Proposal for your review. Generating a proposal never writes to GitHub. A write only ever happens if you explicitly click "Approve and Apply" below on a valid proposal — the server re-verifies everything again immediately before making any change.

Repository Status

Repository
aim4itnow/llm-board-core
Branch
founders-desk-v0
Current SHA
(unavailable)
Unable to verify remote state

The current remote branch HEAD could not be confirmed just now, so no SHA is shown as verified. Reason: Repository aim4itnow/llm-board-core not found (or not visible with the current credentials).

Coding Team Core

These capabilities already exist in code. The Coding Request panel below exercises the proposal and verification capabilities on every click; only an explicit "Approve and Apply" click exercises the write and post-commit verification capabilities.

  • Read repository state
  • Verify expected remote SHA
  • Create governed Change Proposals
  • Apply controlled GitHub changes
  • Create one commit
  • Refuse stale proposals
  • Verify resulting remote commit
  • Fail closed when durability cannot be proven

Coding Team Workflow

This full sequence is implemented in the "Coding Request" panel below: generating a proposal never writes to GitHub, and a write only happens after an explicit human "Approve and Apply" click, which re-verifies remote state before writing and independently re-verifies the resulting commit afterward before reporting completion. Shell execution, test execution, build execution, and deployment are not part of this sequence and are not implemented.

  1. Verify repository state
  2. Prepare Change Proposal against exact SHA
  3. Review / approve
  4. Apply controlled change
  5. Verify resulting remote SHA