REACH + OCTO

Appearance

REACH + OCTODeclare intent. Claude compiles. Live systems answer.

A local workflow practice for Windows. No infrastructure. No always-on agents. Human judgment as a first-class architectural primitive.

What is REACH?
What is OCTO?
GitHub
🎯

Intent, Not Implementation

Write what you want. Claude chooses the library, the connection string, the output shape. You never see COM Interop, NuGet packages, or SQL client boilerplate.

🐙

Eight Arms, One Intelligence

OCTO coordinates multiple REACH arms simultaneously. Each reaches independently. OCTO reads the combined signal and generates the right surface for this moment.

👤

Human-First by Design

The decision surface isn't a safety check. It's the architecture. Human judgment reserved at the moment it matters — not routed around, not deferred. Built in.

🔧

.NET 10, Nothing More

No servers. No pipelines. No dashboards. No Docker. dotnet run task.cs and the reach executes. Everything else is a NuGet package Claude picks for you.

📄

Artifacts Without Infrastructure

Every meaningful reach writes a .reach-artifact — typed, human-readable, git-diffable. Memory without a database. Findings that outlast the session.

🏗️

Methodology-as-Infrastructure

Part of the Semantic Intent ecosystem. CAL decides. EMBER remembers. REACH reaches. OCTO orchestrates. Each a vocabulary. Each a DSL. Each a practice.

What is REACH? ​

REACH is a local workflow practice where you declare what you want to reach into — Outlook, SQL Server, git, a browser, a desktop UI — and Claude compiles it to a typed C# script that runs against your live systems. No pre-built connectors. No fixed implementations. The capability surface is unlimited because Claude picks the library, not you.

A .reach file is the intent layer. Claude is the compiler.

What is OCTO? ​

OCTO is an orchestration pattern built on REACH. Where REACH is a single arm reaching into one source, OCTO coordinates multiple arms simultaneously — each reaching independently, the combined signal surfacing a contextual decision interface at the moment that matters.

Named after the octopus: eight arms, each semi-autonomous, coordinated by one intelligence. The arms find. The octopus decides.

An .octo file is the orchestration intent. Claude is the conductor.

The Morning Brief ​

The canonical demonstration. Five arms. One surface. One decision. One joke.

08:45 — morning.octo runs

Arms reach simultaneously:
  outlook.inbox    → 3 flagged items, 1 urgent thread
  teams.planner    → 2 overdue, 1 due today
  teams.transcript → last standup: deployment mentioned
  git.commits      → 2 commits yesterday, on track

Surface appears:
┌──────────────────────────────────────────────┐
│  Good morning. Here's what needs you.        │
│                                              │
│  🔴 Sarah emailed twice — awaiting reply     │
│  🟡 Project planner item — 3 days overdue    │
│  📋 Deployment flagged in yesterday's standup│
│                                              │
│  [Draft reply to Sarah]                      │
│  [Send morning summary to team]              │
│  [Snooze planner item]                       │
│  [Show me everything]                        │
└──────────────────────────────────────────────┘

OCTO closes:
  "Sarah will appreciate that.
   One less thing before your first meeting."

8:52am. Day begins.

Why Not a Framework ​

Enterprise agentic frameworksREACH + OCTO
SetupInfrastructure required.NET 10 SDK
TokensContinuous burnPer task — bounded
HumanRouted aroundFirst-class architectural primitive
OutputWhenever agents decideWhen you ask
StateFramework-managed, complexFlat files — owned by you

REACH + OCTO are not competitors to LangChain, AutoGen, or CrewAI. They answer a different question:

"How does one person work better tomorrow morning?"

Requirements ​

  • Windows (COM Interop, Task Scheduler, WinForms — deliberately local)
  • .NET 10 SDK
  • Claude Code CLI or any Claude interface
  • Playwright browser binaries — playwright install chromium for browser reaches

Citation ​

bibtex
@misc{shatny2026reach,
  author    = {Shatny, Michael},
  title     = {REACH + OCTO: A Local Workflow Practice and Orchestration Pattern},
  year      = {2026},
  publisher = {Zenodo},
  doi       = {10.5281/zenodo.20680385},
  url       = {https://reach.semanticintent.dev}
}

DOI