Limitless OS HCS Pull Queue Specification
internal prototype · canonical JSON + Dreamborn Forge HTML
internal generated
hcs-pull-queue-spec · supabase_json

Limitless OS HCS Pull Queue Specification

hcs-pull-queue-spec artifact · for Limitless OS · status draft

Planning Surface

Use this to decide what happens next.

Status

draft

Agent Handoff
Start Here

hcs-pull-queue-spec artifact · for Limitless OS · status draft

Completion Evidence

No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.

Artifact Shape
  • title: Limitless OS HCS Pull Queue Specification
  • intent: Use HCS as the canonical pull-queue and audit layer for Limitless agent work. Agents claim tasks from role topics, fetch full context from authorized stores, produce structured outputs, and route sensitive outputs through human gates.
  • source: atlas-codex
  • client id: limitless
  • project id: 07dee66f-8143-4f4d-9af9-b1ed413d2767
  • task shape: brief: string, task_id: string, client_id: string, project_id: string, sensitivity: object, source_refs: object, role_topic_slug: string, completion_contract: object, human_review_required: string
  • updated at: 2026-05-09T19:02:57.675Z
  • queue model: pattern: string, claim_rule: string, read_model: string, topic_types: object
  • project name: Limitless OS
  • artifact type: hcs-pull-queue-spec
  • schema version: 1
  • task lifecycle: 10 items
Structured Payload

Machine-readable source fields

title

Limitless OS HCS Pull Queue Specification

intent

Use HCS as the canonical pull-queue and audit layer for Limitless agent work. Agents claim tasks from role topics, fetch full context from authorized stores, produce structured outputs, and route sensitive outputs through human gates.

source

atlas-codex

client id

limitless

project id

07dee66f-8143-4f4d-9af9-b1ed413d2767

task shape
brief

Self-contained structured task brief

task id

HCS topic/event id or platform task id

client id

limitless

project id

07dee66f-8143-4f4d-9af9-b1ed413d2767

sensitivity
  • low
  • medium
  • high
source refs
  • CRM lead id
  • PT Everywhere reference
  • email thread id
  • voice transcript id
  • content asset id
role topic slug

Target role queue slug

completion contract
  • required output schema
  • review gate
  • forbidden claims
  • evidence refs
human review required

boolean

updated at

2026-05-09T19:02:57.675Z

queue model
pattern

full pull queue with HCS role topics

claim rule

Agents poll their role topic, atomically claim available tasks, write claim event, execute, and post structured completion/block event.

read model

Supabase stores current task, claim, artifact, approval, and dashboard state reduced from HCS events and local system integrations.

topic types
  • project topic
  • role topics
  • human review gate topics
  • audit/event topics
project name

Limitless OS

artifact type

hcs-pull-queue-spec

schema version

1

task lifecycle
  • task.created
  • task.claimed
  • task.started
  • task.output_drafted
  • task.review_requested
  • task.approved
  • task.sent_or_applied
  • task.complete
  • task.blocked
  • task.cancelled
privacy boundary
  • Do not write PHI, payer details, or sensitive staff content directly to public HCS payloads.
  • HCS carries pointers, hashes, status, and structured non-sensitive summaries only.
  • Supabase or client-controlled stores hold sensitive bodies behind access controls.
  • Audit trail must preserve who approved sensitive outbound actions.
role topics seed
  • roles.limitless.ops-chief
  • roles.limitless.voice-capture
  • roles.limitless.lead-intake
  • roles.limitless.content-strategy
  • roles.limitless.content-execution
  • roles.limitless.patient-comms
  • roles.limitless.billing
  • roles.limitless.sop
  • roles.limitless.staff-coach
  • roles.limitless.kpi
  • roles.limitless.clinical-ed
  • roles.limitless.vald
  • roles.limitless.performance-coach
source documents
pathrolepagestitle
/Users/justinking/Downloads/Limitless_OS_Final_Vision_Document.pdfPatient/performance operating system vision19Limitless OS Final Vision & Goals/Intent Document
/Users/justinking/Downloads/Limitless Ai Agent Goals Intent Blueprint.pdfFront-office and business-support agent blueprint40Limitless Physical Therapy & Performance AI Agent Goals & Intent Blueprint
human review gates
gatedefaultreviewerapplies to
clinical_outboundrequiredclinician- clinical advice - return-to-play guidance - treatment-plan language
billing_outboundrequiredBetsy/Seth- payment requests - insurance disputes - collections language
staff_feedbackrequiredSeth- corrective feedback - performance documentation
public_content_sensitiverequiredSeth- patient stories - reputation-sensitive posts - specific local partners
lead_replyrequired_in_v1Betsy/Seth until approved templates exist- standard lead follow-up
completion contracts
  • Every output identifies whether it is draft-only, approved-to-send, or internal-only.
  • Every patient-facing output includes audience, channel, intended human reviewer, and forbidden claims check.
  • Every blocked task includes blocker_type, attempted_steps, missing_inputs, and recommended next action.
  • Every completed task includes structured output_ref and no raw PHI in HCS payload.