orionfold-relay 0.0.1 → 0.15.1

package/LICENSE

@@ -0,0 +1,191 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding any notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2025 Manav Sehgal
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,19 +1,201 @@
 # Orionfold Relay
 
-**The multi-agent coordination cockpit for forward-deployed AI services.**
+> Run a forward-deployed AI agency on one cockpit. Every client a workspace, every vertical a profile, every service a workflow, every model a switch — on one governed, cost-controlled board you own.
 
-Run an AI services agency on one governed, cost-controlled board: every client a
-workspace, every vertical a profile, every service a workflow, every model a
-switch — Claude, Codex, Gemini, or a local model — with per-client billing and
-human-in-the-loop governance built in.
+```bash
+npx orionfold-relay
+```
 
-> **This package name is reserved.** The Relay CLI ships with the public launch.
-> Until then, `npx orionfold-relay` prints a short notice.
+Open [localhost:3000](http://localhost:3000). Zero config, local SQLite, your data stays on your machine.
 
-Part of the Orionfold studio family — **Proof** (which AI can I trust?), **Arena**
-(which build wins?), and **Relay** (now make the trusted AI do the work).
+[![npm](https://img.shields.io/npm/v/orionfold-relay)](https://www.npmjs.com/package/orionfold-relay) [![Next.js 16](https://img.shields.io/badge/Next.js-16-black)](https://nextjs.org/) [![React 19](https://img.shields.io/badge/React-19-61DAFB)](https://react.dev/) [![TypeScript](https://img.shields.io/badge/TypeScript-strict-3178C6)](https://www.typescriptlang.org/) [![Claude Agent SDK](https://img.shields.io/badge/Claude-Agent_SDK-D97706)](https://docs.anthropic.com/) [![OpenAI Codex App Server](https://img.shields.io/badge/OpenAI-Codex_App_Server-10A37F)](https://developers.openai.com/codex/app-server) [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
 
-- Website: https://orionfold.com
-- License: Apache-2.0
+Orionfold Relay is the **operations layer** for AI builders, consultants, and forward-deployed services teams — the missing layer between "run one agent" and "run a managed service for a roomful of clients." You point it at your client work, run multi-step workflows across local and cloud models, route every client-facing deliverable through human approval, and watch per-client cost roll up automatically. It's local-first, open source (Apache-2.0), and ships as one command.
 
-© 2026 Orionfold.
+Relay is the **third** product in the Orionfold line — **Proof** answers *"which AI can I trust?"*, **Arena** answers *"which build wins?"*, and **Relay** answers *"now make the trusted AI do the actual work."* It's the only one whose value compounds *after* evaluation stops.
+
+<img src="https://raw.githubusercontent.com/orionfold/relay/main/public/readme/home-list.png" alt="The Relay home workspace: active work, pending review, project signals, and a live agent activity stream on one board" width="1200" />
+
+---
+
+## Describe an app — Relay builds it
+
+The proof is in what Relay composes, not what it benchmarks. You describe a client module in plain language, and Relay assembles it from its primitives — an agent profile, a workflow blueprint, a schedule, and a table or two — into one running app. No new code, no deploy.
+
+A "receipt photo → bookkeeping" module for a property-management client is one prompt away; the next client who needs the same thing reuses it in minutes. The composed app runs as a first-class instance with its own KPIs, and every agent run under it meters real cost back to that customer — the hardcoded billing line is gone, replaced by live per-client attribution from the usage ledger.
+
+<img src="https://raw.githubusercontent.com/orionfold/relay/main/public/readme/apps-starter-to-chat.png" alt="Describe an app in plain language and Relay composes it from a profile, blueprint, schedule, and tables — no code, no deploy" width="1200" />
+
+| Compose an app | Apps gallery | Inside a composed app |
+|:-:|:-:|:-:|
+| Plain-language prompt → a profile + blueprint + schedule + tables, wired into one running module | Composed apps run as first-class instances alongside ready-made starters | Live KPI tiles plus every service workflow as a one-click run — a whole vertical, composed not coded |
+
+---
+
+## The five gaps every AI agency hits
+
+AI agents can already abstract a lease, research a grant, or categorize a receipt. The gap is everything *around* that — and for an agency, every gap multiplies by the number of clients you serve.
+
+1. **Orchestration** — Real client work is multi-step: ingest, abstract, verify, deliver. Relay runs sequences, checkpoints, and planner→executor pipelines without glue code you'd maintain.
+2. **Strategy → execution** — You think in clients, services, and deliverables; agent tools think in prompts and tokens. Projects, profiles, and blueprints give you a shared language between the engagement and the execution.
+3. **Lifecycle** — A deliverable needs scheduling, retries, resume-from-checkpoint, cost tracking, and an audit trail. Relay carries the whole operational lifecycle; recurring statements and deadline watches run themselves.
+4. **Trust & governance** — Agents that read client files and draft client-facing output need guardrails. Relay routes every deliverable through human approval and keeps the audit trail funders and stakeholders ask for.
+5. **Distribution** — Standing up an agent workspace shouldn't mean cloning a repo and wiring a database. Relay is `npx orionfold-relay` — one command, zero config, your data stays local.
+
+---
+
+## Built for an agency
+
+| Your operating model | Relay primitive |
+|---|---|
+| **Clients** → one workspace per client, with scoped reference docs the agents consult automatically | **Projects** |
+| **Verticals** → CRE underwriting, listing analysis, grant research, impact reporting — each a tuned agent | **Profiles** (21 built-ins) |
+| **Services** → a repeatable, packaged service you instantiate per client with their variables | **Blueprints** (15 templates) |
+| **Deliverables** → weekly digests, monthly statements, deadline watches running on a cadence | **Schedules** |
+| **Billing** → per-client spend allocation that maps to the retainer, with a real margin you can see | **Cost & Usage** |
+| **Governance** → every client-facing deliverable through human approval with a full audit trail | **Inbox** |
+
+<img src="https://raw.githubusercontent.com/orionfold/relay/main/public/readme/tasks-list.png" alt="One Kanban board: multi-step, multi-client work across every status, each card carrying its client, workflow pattern, and assigned agent profile" width="1200" />
+
+---
+
+## The three pillars
+
+### 1 · One cockpit, your whole client book
+Every client is a project with its own scoped documents, tasks, and working directory. One Kanban board replaces a wall of browser tabs and a "who's doing what" spreadsheet: lease abstraction, an offering memo, a grant narrative, receipt intake — across clients, every status, on one screen. Drag-and-drop columns or a sortable table.
+
+### 2 · Multi-vendor, no lock-in
+Different work wants different models, and the best model changes every few months. A shared runtime registry lets you switch providers **per task, per schedule, or per workflow step** without redefining how your agents behave. Run reasoning on **Claude**, code generation on **Codex**, document work on **Gemini**, and route low-stakes or sensitive work to a local **Ollama** model at $0 compute. The cost dashboard shows the blended mix so you can prove the savings.
+
+<img src="https://raw.githubusercontent.com/orionfold/relay/main/public/readme/costs-list.png" alt="Cost & Usage: spend pacing, active provider mix, and per-project allocation that maps straight to a client retainer" width="1200" />
+
+### 3 · Zero-code apps
+Profiles, blueprints, schedules, and tables are the Lego bricks. Describe what you want and Relay composes a running app from them — the fastest way an agency ships a new client module. Package a whole vertical (profiles + workflows + a table + KPIs) as one pure-config bundle and install it in one click.
+
+---
+
+## Customers — now first-class
+
+The customer dimension is **shipped**. Each account you run ops for is a first-class customer record — not a naming convention on a project. Link a customer's projects, and every agent run under them attributes its spend back automatically, so per-client cost is a real rollup from the usage ledger rather than a number you reconcile by hand. That foundation is the seam every pack seeds customers through, and the base for retainer-vs-cost margin.
+
+| The customer book | A customer detail view |
+|:-:|:-:|
+| <img src="https://raw.githubusercontent.com/orionfold/relay/main/public/readme/customers-list.png" alt="The customer book: each account labeled by vertical, with linked projects and a 30-day cost rollup per customer" width="580" /> | <img src="https://raw.githubusercontent.com/orionfold/relay/main/public/readme/customers-detail.png" alt="A customer detail view: linked projects and AI spend rolled up from real agent runs — live per-client attribution, not a hardcoded billing line" width="580" /> |
+
+---
+
+## Orchestration — simple to governed
+
+A workflow is how a repeatable service runs itself. The same screen runs **six patterns**:
+
+- **Sequence** — a clean chain of steps an agent works top to bottom
+- **Planner→Executor** — one agent plans, another executes each step
+- **Human-in-the-Loop Checkpoint** — pauses at approval gates so nothing client-facing ships without sign-off
+- **Parallel** — 2–5 concurrent branches followed by one synthesis step
+- **Loop** — iterative execution with configurable stop conditions
+- **Swarm** — mayor → worker pool → refinery orchestration
+
+The governance is *in* the workflow, not bolted on. A blueprint is a fixed step shape plus a Configure form — fill in a client's variables and it becomes a ready-to-run workflow, the same service instantiated for the next client in minutes.
+
+<img src="https://raw.githubusercontent.com/orionfold/relay/main/public/readme/workflows-blueprints.png" alt="Workflow blueprints: a fixed step shape with per-step agent profile and approval gates, plus a Configure form to instantiate per client" width="1200" />
+
+---
+
+## Why it stays trustworthy
+
+- **Local-first** — SQLite database, no cloud dependency, `npx orionfold-relay` and go
+- **Your rules, enforced** — tool permissions, inbox approvals, and audit trails for every agent action
+- **Your AI team** — 21 specialist profiles ready to deploy, each with instructions, tool policies, and runtime tuning
+- **Know what you spend** — usage metering, budgets, and per-provider/per-model spend visibility on governed runs
+- **Open source** — Apache-2.0, read the engine and run it yourself
+
+<img src="https://raw.githubusercontent.com/orionfold/relay/main/public/readme/inbox-list.png" alt="The governance command center: tool-permission approvals, agent questions, and a permission queue — nothing reaches a client without sign-off" width="1200" />
+
+---
+
+## Runtime bridge
+
+Run the same business process on different AI providers without changing a line of configuration. Relay's shared runtime registry routes tasks, schedules, and workflow steps through **Claude Code** (Anthropic Claude Agent SDK) and **OpenAI Codex App Server**, landing everything in the same inbox, monitoring, and cost surfaces. Switching providers is a settings change, not a rewrite.
+
+---
+
+## Tech stack (boring on purpose)
+
+| Layer | Technology | Why |
+|-------|-----------|-----|
+| Framework | Next.js 16 + React 19 | Server Components for zero-API reads, Turbopack for fast dev |
+| Language | TypeScript (strict) | End-to-end type safety from DB schema to UI |
+| Styling | Tailwind CSS v4 + shadcn/ui | Utility-first CSS with accessible component primitives |
+| Database | SQLite (WAL) + Drizzle ORM | Zero-config embedded DB, type-safe queries, concurrent reads |
+| AI Runtime | `@anthropic-ai/claude-agent-sdk` + `codex app-server` | Governed Claude and OpenAI execution behind a shared runtime layer |
+| CLI | Commander + tsup | Familiar CLI framework, fast ESM bundling |
+| Testing | Vitest + Testing Library | Fast test runner with React component testing |
+| Validation | Zod v4 | Runtime type validation at system boundaries |
+
+npm distribution name: `orionfold-relay` (CLI commands `relay` / `orionfold-relay`).
+
+---
+
+## Development
+
+```bash
+git clone https://github.com/orionfold/relay.git && cd relay && npm install
+
+# Set up one or both runtime credentials
+cat > .env.local <<'EOF'
+ANTHROPIC_API_KEY=your-anthropic-key
+OPENAI_API_KEY=your-openai-key
+EOF
+
+npm run dev            # Next.js dev server (Turbopack)
+npm run build:cli      # Build CLI → dist/cli.js
+npm test               # Run Vitest
+npm run test:coverage  # Coverage report
+npm run test:e2e       # E2E integration tests (requires runtime credentials)
+```
+
+### Pull requests
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/your-feature`)
+3. Make your changes and add tests
+4. Run `npm test` and `npx tsc --noEmit`
+5. Submit a pull request
+
+See `AGENTS.md` for architecture details and development conventions, and `CHANGELOG.md` for release history.
+
+---
+
+<details>
+<summary><b>Full feature inventory</b> — 211 features shipped across the platform</summary>
+
+All 14 MVP features shipped (CLI bootstrap, database schema, app shell, project management, task board, agent integration, inbox notifications, monitoring, homepage dashboard, workflow engine, AI task assist, content handling, session management). 197 more shipped post-MVP:
+
+| Category | Highlights |
+|----------|-----------|
+| **Documents** (5) | File attachments, preprocessing (5 formats), agent context injection, document browser, output generation |
+| **Agent Intelligence** (6) | Multi-agent routing, autonomous loops, multi-agent swarm, AI assist→workflows, agent self-improvement, workflow context batching |
+| **Agent Profiles** (2) | Agent profile catalog (21 profiles), workflow blueprints (15 templates) |
+| **UI Enhancement** (13) | Ambient approvals, learned-context UX, micro-visualizations, command palette, accessibility, kanban operations, board persistence, playbook docs, workflow UX overhaul |
+| **Platform** (8) | Scheduled prompt loops, tool permissions, provider runtimes, OpenAI Codex runtime, cross-provider profiles, parallel fork/join, tool permission presets, npm publish |
+| **Runtime Quality** (2) | SDK runtime hardening, E2E test automation |
+| **Governance** (3) | Usage metering ledger, spend budget guardrails, cost & usage dashboard |
+| **Chat** (12) | 5-tier context engine + CRUD tools, SSE streaming, tool catalog, skill composition, `#key:value` filters, saved searches, conversation branching/rewind (`⌘Z`/`⌘⇧Z`), chat-driven app builder |
+| **Composed Apps** (10) | `/apps` surface, starters showcase, 6 layout kits (Tracker, Coach, Ledger, Inbox, Research, Workflow Hub), manifest authoring tools, atomic writes, KPI ratio composition |
+| **Onboarding** (2) | First-launch runtime preference modal (Best quality / Balanced / Lowest cost / Best privacy), instance bootstrap with dev-mode gate |
+| **Customers** (first-class) | Hard `customers` table, write-time cost attribution, per-customer rollup, `/customers` list + detail |
+| **Plugin Platform** (5) | Chat-tools plugin kind, MCP plugin spec, plugin tools registry, plugin spec tools, schedule spec tools |
+| **Platform Hardening** (2) | Runtime validation hardening, upgrade detection (hourly upstream poll + guided merge sessions) |
+| **Environment** (11) | Scanner, cache, dashboard, git checkpoint manager, sync engine, project onboarding, templates, cross-project comparison, skill portfolio, health scoring, profile-from-environment |
+
+See `features/roadmap.md` for the full inventory and `features/stats/snapshot.json` for canonical counts.
+
+</details>
+
+---
+
+## License
+
+Licensed under the [Apache License 2.0](LICENSE).
+
+Copyright 2025–2026 [Manav Sehgal](https://github.com/manavsehgal)

package/components.json

@@ -0,0 +1,21 @@
+{
+  "$schema": "https://ui.shadcn.com/schema.json",
+  "style": "new-york",
+  "rsc": true,
+  "tsx": true,
+  "tailwind": {
+    "config": "",
+    "css": "src/app/globals.css",
+    "baseColor": "zinc",
+    "cssVariables": true,
+    "prefix": ""
+  },
+  "aliases": {
+    "components": "@/components",
+    "utils": "@/lib/utils",
+    "ui": "@/components/ui",
+    "lib": "@/lib",
+    "hooks": "@/hooks"
+  },
+  "iconLibrary": "lucide"
+}