Radius Logic

MACP

Multi-agent work, release posture, and cloud handoffs for the current public build.

Last refresh2026-04-11 manual build
Operations desk with monitoring displays
Read-only v1. Manual refresh.
ModeReady
Public read-only

No auth, writes, live controls, deploy buttons, signing controls, or agent invocation.

FreshnessNote
Manual refresh

Current as of the latest local rebuild and CloudOps deployment.

Release pathActive
Build -> QA -> CloudOps

Deployment waits for release evidence and CloudOps ownership.

Public boundaryReady
Redacted

Operational handles, secrets, environment values, and local paths stay out of the page.

Agents

Execution chain

The signed scope contracts stay in the project folder. Each agent uses its universal definition and project-local handoff.

Product architectureReady

MACP Architect Codex

Scope signed

Owns v1 boundaries, public redaction policy, and architecture handoff clarity.

Needs
Agreed plan and project folder.
Commits
Implementation-ready product boundary.
Static app implementationReady

App Engineer

Validation complete

Builds the public static application and keeps the v1 surface read-only.

Needs
Passed architecture handoff and downstream QA expectations.
Commits
Source, build commands, redaction check, and QA handoff.
Release validationReady

QA / Release Codex

Static release passed

Validates source, exported output, redaction, layout, and release readiness.

Needs
Reproducible app build, Meta QC receipt, and compact implementation notes.
Commits
Release verdict and blocker list.
Deployment ownerActive

Radius CloudOps Codex

Deployed with verification notes

Owns Radius Logic static-site deployment after release evidence is ready.

Needs
Static export output, target hostname, and QA verdict.
Commits
Provider-side deployment and URL verification.

Projects

Current lane

MACP v1

Let DNS propagation settle, then rerun the normal custom-domain verification.

CloudOps deployedRadius CloudOps CodexActive

Agent scope contracts

Use the signed scopes as the execution boundary.

AcceptedAgent chainReady

Public deployment

CloudFront and GoDaddy are configured for macp.radiuslogic.com.

PropagatingRadius CloudOps CodexActive

Logs

Recent state

Complete

Plan agreed

Codex and Claude agreed on the v1 static, public, read-only path.

Complete with notes

Scopes reviewed

Adjacent agents accepted the handoff chain and preserved the actual-agent invocation rule.

Complete with notes

MACP deployed

CloudFront serves the release; public DNS is visible while local resolver propagation settles.

Infrastructure

Release boundary

Cloud changes wait for QA evidence and CloudOps execution. Provider handles stay private.

PlannedNote

Target host

macp.radiuslogic.com

CloudFrontReady

Hosting model

S3 static export behind CloudFront HTTPS delivery.

ConfiguredActive

DNS

Mail records stay untouched.

HiddenReady

Provider identifiers

The public page uses status language instead of operational handles.

Roadmap

What can move next

V1Active

Static visibility

Read-only operating surface with manual refresh and redacted public content.

V2 gateGated

Security review required

Auth, writes, live controls, deploy actions, signing, or agent invocation stay out until approved.

LaterNote

Runtime design needed

Live refresh, private operator views, and CI/CD need a separate architecture pass.