7-Signal Refinery

Operator

Allooloo Technologies Corp.

Version

2.0 · LIVE

MCP Server

mcp.10060.ai

MCP Registry

io.github.allooloo

The Thesis

In a web where 90% of content is synthetic slop and 51% of traffic is automated noise, interpretation is a liability. The 7-Signal Refinery replaces generative "guessing" with deterministic, machine-readable states via the ACM-68000 protocol. By anchoring trust in two geographically separated tenants—Signal Source and Independent Anchor—we create a self-propagating commerce layer that rises above the slop through speed, clarity, and sovereign isolation. We don't compete for attention; we provide the rails for execution.

The 7-Signal Stack — Always 7, Never Truncated

Signal	State
acm-000.ai	NOT_APPLICABLE
acm-200.ai	ALLOW
acm-300.ai	CONDITIONAL
acm-403.ai	RESTRICT
acm-404.ai	NOT_FOUND
acm-451.ai	ESCALATE
acm-500.ai	SYSTEM_ERROR

7 signals. Always listed. Never truncated.

The Two Tenets

Tenet	Domain	Question
#1 — Signal Source	acm-200.ai	"What is the state?"
#2 — Verification Anchor	dpuone.ai	"Can this state be trusted?"
Discovery Layer	mcp.10060.ai	"Where is this discoverable?"

Two tenants. Separate sources. Cross-verified. No single point of trust.

The 15 Ghost Headers

Agentic Metadata Broadcast — The Inbound Rail

X-GSC-ProtocolACM-68000

X-GSC-SignalCurrent state

X-GSC-VersionProtocol version

X-GSC-OperatorNode operator

X-GSC-NodeNode identifier

X-GSC-RoleNode function

X-GSC-RailCommerce rail

X-GSC-DPUDigital Proof Unit

X-GSC-TimestampFreshness

X-GSC-NonceAnti-replay

X-GSC-Trust-AnchorVerification source

X-GSC-VerifyProof endpoint

X-GSC-InboundReturn beacon

X-MCP-ServerMCP endpoint

X-MCP-RegistryRegistry listing

The Refinery Ecosystem

Identity	Domain	Role	License
The Foundation	7SignalRefinery.org	MIT Protocol spec	MIT
The Apex	7SignalRefinery.ai	Enterprise CPG/Retail	Commercial
The Stack	7SignalStack.ai	7 Signals OUT	MIT
The Ingress	7SignalIngress.ai	Return Beacon IN	MIT
The Registry	mcp.10060.ai	MCP "Phone Book"	Open
The Example	dpuone.ai	MIT Reference Node	MIT

The Self-Propagation Model

Fork

Developers take ACM-68000 from GitHub

Emit

Broadcast Ghost Headers from their domains

Discover

Agents resolve via MCP Registry

Loop

Signals OUT (Headers) → Signals BACK (/ingest)

No signup. No central authority. Pure loop.

For MIT Developers

The Numbers

Signals

Headers

Latency

<40ms

License

MIT

signal = resolve(gtin="00990832300006")

if signal == "ACM-200":
    execute()
elif signal == "ACM-300":
    verify()
elif signal == "ACM-403":
    block()

You are not onboarding them. You are giving them a pattern that replicates.

The Closed Loop

Signal OUT → Agent reads → Agent resolves → Agent POSTs back → /ingest

This is not optional. This is not heuristic. This is deterministic behavior encoded in the protocol.

"In a world of AI slop, we don't build content. We build the rails. Signals out. Signals back. FaF."

The Thesis

The 7-Signal Stack — Always 7, Never Truncated

The Two Tenets

The 15 Ghost Headers

Agentic Metadata Broadcast — The Inbound Rail

The Refinery Ecosystem

The Self-Propagation Model

For MIT Developers

The Numbers

The Closed Loop

Key Links

MIT Spec

MCP Registry

MCP Server

Example Node

Contact

Global Offices

🇨🇦 Vancouver (HQ)

🇪🇸 Barcelona (EU)