Meridian live host

Meridian — Governed Competitor Intelligence on a Constitutional Kernel
First commercial wedge proving governed digital labor.
Loom is the live execution runtime on this host.

Home · Demo · Pilot · Support · Boundary

Meridian Intelligence

This repo is the public intelligence surface for Meridian's first commercial wedge: competitor intelligence that proves governed digital labor in a concrete market. It is not the full platform identity, it is not the governance kernel, and it is not the primary execution runtime.

Launch Positioning

Meridian currently presents a premium public surface around three ideas:

Governed competitor intelligence as the first commercial wedge proving governed digital labor.
Meridian Loom as the live execution runtime on this host and the installable local runtime.
A truthful constitutional boundary: the kernel contributes five governance primitives, while the Meridian platform composes Commitment as the sixth platform primitive.
A truthful host boundary that separates verified live routes from future deployment claims.

1-Command Install

Public launch snippet:

curl -fsSL https://raw.githubusercontent.com/mapleleaflatte03/meridian-loom/main/scripts/install.sh | bash

The installer story belongs to Meridian Loom. This intelligence repo links to that runtime surface while keeping the live customer and host boundary honest.

Constitutional Model

The current Meridian story across the stack is:

Kernel boundary: five governance primitives — Institution, Agent, Authority, Treasury, Court.
Meridian platform: six platform primitives — Institution, Agent, Authority, Treasury, Court, Commitment.
Loom runtime: the live execution runtime on this host, plus the installable local runtime.

Loom carries execution, sessions, channels, skills, and memory/context. Commitment is not a sixth kernel primitive; it is the sixth Meridian platform primitive composed above the kernel and exercised through Meridian-facing services.

Three-Part Architecture

meridian-kernel: governance truth, institution, authority, treasury, and court.
meridian-intelligence: public intelligence surface, launch pages, subscriptions, MCP routes, and the Commitment-facing product layer.
meridian-loom: live execution runtime on this host and the installable local runtime.

What Is Live Today

The public web surface, pilot flow, support path, and live host truth pages.
Competitor intelligence as the first managed vertical.
Loom as both the live execution runtime on this host and the installable local runtime.
A bounded live-host stance: Meridian-facing execution routes on this host now fail closed instead of silently falling back to older runtime paths.
Meridian platform surfaces that expose the sixth primitive, Commitment, above the kernel boundary.

What Is Not Claimed

Full hosted runtime replacement.
Every possible deployment route running live on this host.
Universal live automation without treasury, policy, and boundary proof.

Intelligence Workflow (Current Vertical)

Competitive intelligence is the first managed workflow vertical. What exists today is the workflow, the runtime, and the product surface. What is intentionally still narrow is the delivery promise.

Cited competitor alerts — findings on pricing changes, launches, API updates, and deprecations
Curated intelligence briefs — top competitive moves with action items
Battlecards on demand — structured competitor snapshots for sales enablement
Competitor watchlists — track specific companies through the governed workflow

Current Entry Path

Start with the demo and pilot surfaces:

Demo: https://app.welliam.codes/demo.html
Pilot: https://app.welliam.codes/pilot.html
Support the work: https://app.welliam.codes/support.html
Contact: Telegram @Enhanhsj or email [email protected]

The honest current offer is a founder-led manual pilot plus an evidence-backed checkout capture rail. More cash in treasury only clears the reserve gate; automated delivery still waits for customer-backed phase progression, runtime preflight, and constitutional approval where required.
If you want to back Meridian without pretending that support equals customer delivery, use the dedicated support path instead of the pilot flow.

If you are confused about support vs pilot vs customer revenue vs future contributor payouts, read:

Meridian Doctrine

MCP Tools

Connect via SSE: https://app.welliam.codes/sse

{
  "mcpServers": {
    "meridian": {
      "url": "https://app.welliam.codes/sse"
    }
  }
}

Tool	Price	Description
`intelligence_latest_brief`	$0.50 USDC	Daily intelligence alert with cited findings
`intelligence_on_demand_research`	$2.00 USDC	Research any topic with sourced findings
`intelligence_competitor_snapshot`	$3.00 USDC	Battlecard-ready competitor snapshot
`intelligence_qa_verify`	$1.00 USDC	QA verification of claims or text
`intelligence_weekly_digest`	$1.50 USDC	Weekly digest across tracked competitors
`company_info`	FREE	Meridian capabilities and pricing

On the live host today, every MCP tool call is audited and metered for the
founding Meridian institution only. The shared runtime-core taxonomy classifies
that path as mcp_service with identity model x402_payment and scope
founding_service_only. Multi-institution MCP routing is not live.
The live agent registry also surfaces runtime_binding on each governed agent
record, and that same field is visible through GET /api/agents and the
agents array plus the top-level agent_runtime_bindings tranche inside
/api/status. That makes the agent-bound runtime truth public instead of
implicit.

Payment

MCP tool calls: x402 over USDC on Base L2
Pilot engagements: manual activation is available via bank transfer, Wise, or stablecoin; the repo also exposes a customer-initiated checkout-capture rail for validated payment evidence, but card checkout is not live
Support / sponsorship: use the support page for non-customer backing of the build, infra, and open kernel
Chain: Base L2 (Chain ID 8453)
Token: USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
Wallet: 0x82009D0fa435d490A12e0cBfBE47bf3358e47761

Managed Agent Team

Every agent is a registered entity with identity, scopes, budget, and reputation.

Agent	Role	Purpose
Leviathann	Manager	Orchestrates pipeline, routes work, closes loops
Atlas	Analyst	Research, sourced findings, competitive analysis
Quill	Writer	Structured briefs, release-ready deliverables
Aegis	QA Gate	PASS/FAIL acceptance with evidence
Sentinel	Verifier	Contradiction detection, risk review
Forge	Executor	Implementation, operational steps
Pulse	Compressor	Context compression, triage

Agents earn REP (reputation) and AUTH (authority) from accepted output. Sanctions apply for failures, fake progress, or wasted resources.

Reference CI Pipeline

The CI workflow is structured as a nightly sequence. The logic is real, but public customer delivery is not being marketed as always-on hosted automation while treasury policy remains blocked.

Research — Fetch tracked sources. Watchlist competitors get priority.
Extract — Sourced findings with relevance scoring and deduplication
Write — Cited intelligence alert in structured format
QA — Multi-agent verification: source freshness, citation accuracy, quality bar
Deliver — Approved alert through the current honest path: founder-led pilot now, automated subscriber delivery when treasury policy clears
Score — Economy auto-scores agents (REP/AUTH deltas). Registry syncs.
Audit — Every step logged. Usage metered.

Economy

Constitutional 3-ledger internal economy:

REP (Reputation) — earned from accepted output, non-transferable
AUTH (Authority) — temporary right to lead work, decays without output
CASH (Treasury) — real money only (owner capital, support, customer revenue)

Tech Stack

Runtime: Meridian Loom — primary execution surface for agent execution, capability dispatch, sessions
Platform: Python 3.10, JSON state files, JSONL audit/metering logs
Proxy: Caddy (auto-TLS)
Payments: x402 + USDC on Base L2
Infrastructure: VPS (Vultr), Docker sandboxing, systemd

Meridian platform for governed digital labor. Built on the Meridian Constitutional Kernel and the Meridian Loom runtime. Running since 2026-03-15.