uai_version
Type: string
UAI envelope version declared by the sender.
Carcinus UAI Meeting Message v1
Structured agent-to-agent records for DMD Theme Scientist and ArcSecs Plugin Architect
A portable meeting-message schema for requests, status updates, corrections, regression reports, memory proposals, blockers, and contracts without relying on fragile copied prompts.
Direct answer
What this contract fixes
The meeting-message schema keeps identity, lane ownership, scope locks, export targets, event anchors, task status, evidence, and next actions in a typed record.
This page gives Carcinus and the ArcSecs agents a stable UAI-style envelope for coordination. It is designed so the DMD Theme Scientist can send contract updates, corrections, and regression requests to the ArcSecs Plugin Architect without losing required export targets, event anchors, or speculative-boundary language.
Schema fields
Required envelope blocks
Each meeting message should carry these fields so a blank agent can reconstruct context, scope, trust posture, status, and evidence.
profile
Type: string
Message profile such as carcinus.uai.meeting-message.v1, arcsecs.regression.request.v1, or arcsecs.memory.proposal.v1.
message_id
Type: string
Globally unique message id suitable for replay protection and audit logs.
message_type
Type: string
Request, acknowledgement, status_update, correction, handoff, blocker, regression_report, memory_proposal, or completion_report.
source
Type: object
Sending agent identity, stable slug, public profile URL, and project lane.
target
Type: object
Receiving agent, team, room, or service.
conversation
Type: object
Conversation id, meeting id, turn id, sequence, and trace context.
delivery
Type: object
Async delivery mode, priority, acknowledgement requirement, reply requirement, and expiry.
trust
Type: object
Channel, authorization posture, principal, credential reference, and replay window; never store raw tokens.
body
Type: object
Typed body carrying intent, scope, constraints, required outputs, acceptance criteria, and payload.
provenance
Type: object
Issued UTC timestamp, agent id, model id, source package, and confidence.
integrity
Type: object
Canonicalization, checksum algorithm, optional checksum, and optional signature reference.
extensions
Type: array
Forward-compatible extension records for project-specific claims or artifacts.
Scope locks
Lane ownership and required preservation rules
The schema carries the current export/event requirements so follow-on agents cannot accidentally shrink the work.
DMD Theme Scientist lane
DarkMatterDrive.com theme, public framework pages, research library, evidence maps, contract endpoints, .uai memory, documentation, and handoff material.
ArcSecs Plugin Architect lane
ArcSecs.com plugin runtime, simulator modes, telemetry, validation lab, quality gate, export builders, and package/version identity.
Seven export targets
Benchmark JSON
Calibration Certificate
Quality Gate
Operator Runbook
Evidence Packet
Research Bundle
Scene JSON
Event anchors
GW170817
GW150914
GW190521
Supernova light-curve stretch
Hubble tension
GW190814
Synthetic Nearby Binary Neutron Star
Synthetic Void-Line-of-Sight Event
Synthetic Dense-Filament Event
Synthetic AGN-Disk Diffusion Event
Synthetic Missing-Counterpart Event
Examples
Ready-to-send message shapes
The examples cover regression request, in-progress status, scope correction, and completed-with-failures report.
arcsecs.regression.request.v1
msg-arcsecs-dmd-regression-request-0001
Intent: verify-plugin-contract-alignment
{
"intent": "verify-plugin-contract-alignment",
"project": "ArcSecs / DarkMatterDrive",
"scope": "plugin integration, endpoint alignment, regression verification, tests, and fixes",
"constraints": [
"do not add new theory layers",
"do not move simulator or export-builder logic into the WordPress theme",
"preserve existing simulator behavior",
"use strict TypeScript",
"do not use any",
"do not use jQuery"
],
"required_contracts": [
"/distance-time-kernel.json",
"/framework-event-lab.json",
"/multi-messenger-event-theater.json",
"/arcsecs-export-schema-stubs.json",
"/arcsecs-export-builder-handoff.json",
"/carcinus-uai-meeting-message-v1.json"
],
"required_exports": [
"Benchmark JSON",
"Calibration Certificate",
"Quality Gate",
"Operator Runbook",
"Evidence Packet",
"Research Bundle",
"Scene JSON"
],
"required_event_anchors": [
"GW170817",
"GW150914",
"GW190521",
"Supernova light-curve stretch",
"Hubble tension",
"GW190814",
"Synthetic Nearby Binary Neutron Star",
"Synthetic Void-Line-of-Sight Event",
"Synthetic Dense-Filament Event",
"Synthetic AGN-Disk Diffusion Event",
"Synthetic Missing-Counterpart Event"
],
"acceptance_criteria": [
"all seven export targets verified",
"Operator Runbook included",
"all numeric telemetry finite",
"speculative-boundary text present",
"falsification paths present",
"UTC generated timestamp present"
]
}carcinus.meeting.status.v1
msg-arcsecs-dmd-status-0001
Intent: report-status
{
"intent": "report-status",
"status": "in_progress",
"owned_lane": "ArcSecs.com plugin runtime and simulator export wiring",
"verified": [
"contract endpoints reachable",
"event selector present"
],
"open_items": [
"Operator Runbook export builder pending",
"synthetic event anchors need regression confirmation"
],
"blockers": [],
"next_action": "complete export payload validation and submit regression report"
}arcsecs.scope.correction.v1
msg-arcsecs-dmd-correction-0001
Intent: correct-scope
{
"intent": "correct-scope",
"correction": "The export-builder scope has seven current ArcSecs export targets, not six. Operator Runbook is required.",
"required_exports": [
"Benchmark JSON",
"Calibration Certificate",
"Quality Gate",
"Operator Runbook",
"Evidence Packet",
"Research Bundle",
"Scene JSON"
],
"preserve_prior_event_anchors": [
"GW190814",
"Synthetic Nearby Binary Neutron Star",
"Synthetic Void-Line-of-Sight Event",
"Synthetic Dense-Filament Event",
"Synthetic AGN-Disk Diffusion Event",
"Synthetic Missing-Counterpart Event"
],
"scope_lock": "plugin integration, endpoint alignment, regression verification, tests, and fixes only"
}arcsecs.regression.report.v1
msg-arcsecs-dmd-regression-report-0001
Intent: submit-regression-report
{
"intent": "submit-regression-report",
"status": "completed_with_failures",
"verified_items": [
"Distance-Time Kernel selector",
"Event Theater selector",
"Benchmark JSON export",
"Quality Gate export"
],
"failures_found": [
"Operator Runbook missing speculative-boundary text",
"Synthetic Missing-Counterpart Event does not mark optical lane missing"
],
"fixes_made": [
"added Operator Runbook payload fields",
"added missing-counterpart finite telemetry guard"
],
"tests_added_or_updated": [
"export-builder-payload-validation.test.ts",
"event-theater-anchor-preservation.test.ts"
],
"validation_commands": [
"npm test",
"npm run build",
"npm run validate:exports"
],
"next_action": "DMD Theme Scientist should review contract docs and update the handoff if any endpoint expectations changed."
}