Pinionize®: From Linked GitHub Repo to Completed Sprint in Minutes, Not Weeks

A closed Beta by Level Up Labs that connects your repository to the Pinion planning and execution workflow with disposable, encrypted shadow workspaces for secure isolation, verified maintainer trust, and delivery through pull requests from your canonical tree.

Pinionize agentic workflow

Pinionize: Plan the sprint, run the sprint, run the retro... all without leaving your active tab.

  • Repeatable, inspectable planning (units, dependencies, frontier) aligned with PR-based delivery.
  • Shadow execution (via H-Frame) so planning artifacts stay under H-Frame topology while app changes land on GitHub.
  • Same HTTP API for the web console and MCP—humans and coding agents share one path.
Watch the demoSchedule a demo / early access

Pinionize® control plane

Level Up Labs · Web + MCP → API → shadow workspace → GitHub

Pinionize API
  • Session auth, repos, verify
  • POST /api/pinion
  • PinionRun history (bounded)
Shadow workspace
  • user-repo/ ↔ GitHub
  • H-Frame topology/pinion
  • Nested shadowrepo layout
GitHub
  • Verified .pinionize/verify.txt
  • PRs from maintainer branch
  • Git as system of record

list → frontier → go → release → retro

See it run

Pinionize demo

Three panes in order: plan the sprint, run Pinion Go, then close with a retro—the same loop Pinionize drives from the browser or MCP.

Planning often either litters the upstream repo with engine files or lives only on a laptop—hard to share with agents and hard to prove you control the remote before automation pushes code.

Pinionize runs Pinion inside a shadow workspace, drops planning under H-Frame topology/, and ships application changes via PRs from user-repo/. Maintainer verification ties durable trust to your GitHub coordinates—then bootstrap, plan-sprint, go, and retro share the same API everywhere.

Sprint Planning

Structure the backlog into ordered work: stories, dependencies, and a frontier ready for execution.

Pinion Go

Run the sprint: agents execute planned work and land application changes as reviewable pull requests.

Sprint Retro

Close the loop: review what shipped, capture lessons, and feed the next planning cycle.

Beyond the foundation

Pinionize: what you get

MVP scope today: identity, repo linking, maintainer verify, shadow execution, Pinion line over HTTP, web console, MCP adapter, and containerized deploy paths—aligned with the product direction for ephemeral shadows and minimal durable sensitive state.

Sign up, sign in, session-based access to API and UI.
Connect a GitHub repo by URL; list linked repos; idempotent duplicate rules.
Maintainer proof via .pinionize/verify.txt with server-issued challenge on the default branch.
Verified repo row in the database—trust persists across sessions and shadow recycle (direction).
Shadow directory per repo: user-repo/ for GitHub, H-Frame topology/pinion for Pinion.
Run any supported Pinion line via POST /api/pinion; output + pr_url when a PR opens.
In-product first-sprint checklist and command legend in the web app.
MCP tools mirror auth, repos, verify, and pinion—parity with the console.

Next step

Ready to wire GitHub to Pinion with verified trust?

Contact Level Up Labs to schedule a demo, get an install-ready build, or talk early access for your maintainers and agent stack.