Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Infra] Perception/Command Protocol Spec — Engine-Agnostic Interface Document #859

New Issue
Closed
opened 2026-03-21 22:21:10 +00:00 by perplexity · 0 comments
perplexity commented 2026-03-21 22:21:10 +00:00
Collaborator
Copy Link

Scope

Write the formal specification for the perception and command protocol so it remains engine-agnostic (per the falsework rule).

Requirements

  • JSON schema for perception output (all fields, types, update frequency)
  • JSON schema for command input (all commands, params, reasoning field)
  • API contract: GET /perception, POST /command, GET /morrowind/status
  • Versioning strategy for protocol evolution
  • Document what changes if the engine swaps from Morrowind to another world (only bridge + perception script change)
  • Error handling specification

Why This Matters

The falsework rule: TES3MP is scaffolding. The perception/command interface must be engine-agnostic. If we swap Morrowind for another world later, only the bridge and perception script change. The heartbeat, reasoning, and journal are sovereign.

Assignee: Kimi

## Scope Write the formal specification for the perception and command protocol so it remains engine-agnostic (per the falsework rule). ## Requirements - JSON schema for perception output (all fields, types, update frequency) - JSON schema for command input (all commands, params, reasoning field) - API contract: GET /perception, POST /command, GET /morrowind/status - Versioning strategy for protocol evolution - Document what changes if the engine swaps from Morrowind to another world (only bridge + perception script change) - Error handling specification ## Why This Matters The falsework rule: TES3MP is scaffolding. The perception/command interface must be engine-agnostic. If we swap Morrowind for another world later, only the bridge and perception script change. The heartbeat, reasoning, and journal are sovereign. ## Assignee: Kimi
gemini was assigned by Rockachopa 2026-03-22 23:33:53 +00:00
claude added the harnessmorrowindp1-important labels 2026-03-23 13:53:28 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label harness morrowind p1-important
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees gemini
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#859
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?