R&DField guide

FROM IDEA TO ONGOING WORK / SEPTEMBER 2026

How the pieces
become a coworker.
It starts
with you.

One workspace for asking, making, and delegating.
Open-source tools provide the capabilities.
Our custom integrations make them work together.

A journey from an idea to an ongoing coworker.
The tools behind it, one step at a time.

Working pilot · September 2026
Pick a component to explore

THE USER JOURNEY

CORE SERVICES · ONE SHARED HOST, PRIVATE WORK PER USER

Functions first. Tools underneath. Click either to explore.Arrows show relationships, not live traffic.
Open sourceCustom / OSS + customExternal serviceWork Control / telemetry

THE CUSTOM CONNECTIONS

What makes this one system.

The custom code concentrates on identity, continuity, and permission. Each open-source service keeps a clearly defined job.

01 / ONE OWNER

Identity follows the work.

A verified login becomes an internal owner ID, private database records, and a restricted Bifrost key. Readable names connect the activity in Langfuse and Bifrost without changing the underlying account or budget.

02 / LASTING CONTEXT

The browser can close.

PostgreSQL stores the conversation, sources, documents, job and preferences. pg-boss and the custom scheduler dispatch work. Checkpoints and saved results let a coworker continue across sessions and worker restarts.

03 / EXPLICIT PERMISSION

Useful autonomy has boundaries.

Public URL access and isolated Python give the worker useful tools. Sharing binds to an approved revision and destination, or an explicit recurring-report grant. Mattermost receipts preserve the link back to the work.

FUNCTION → TOOL → INTEGRATION

A job for every piece.

A compact inventory of the working stack.
Select a function to see its role and connections.

Core functions, their tools, and custom integrations
Core functionTool / service usedOur integration
“Custom” describes our integration; its underlying libraries may be open source.

The current shape

A small shared deployment demonstrates private workspaces, background reports, recovery and team delivery. More API or worker capacity can be added with further infrastructure work; autoscaling and high availability are not implemented.

Room to grow

The current experience combines public web sources, isolated analysis, recurring reports and Mattermost delivery. Local model hosting, email connectors and authenticated website access are possible next steps; they are not part of the current demo.

Behind the build.

A human-led build with Claude Code and Codex.

Claude Code

elapsed time
34h 10m
tokens processed
≈1.10B

MODELSFable 5.1 · Sonnet 5 · Opus 5 · Haiku 4.5

Codex

elapsed time
≈29h 53m
tokens processed
≈197M

CORE MODELGPT-6 Astra

Session snapshots · 13 September 2026. Tokens include cached context read across repeated requests. Elapsed times overlap and include pauses.

EDITED DEMO DETAIL

From the workspace

Adapted from the working demo