StreamDeck v2.8 MCP Actions Registry pilot

[sergstack]

Goal

Create a small supervised MCP Actions Registry pilot for StreamDeck v2.8.

The goal is to move from MCP server connectivity evidence to a usable, approved action layer that ChatGPT/Codex can list and execute safely.

Current context

PR #76 records that:

• Elgato MCP Server is installed and configured for Codex as elgato_streamdeck.
• Stream Deck app has Enable MCP Deck enabled.
• MCP handshake succeeded.
• Observed tools:
  • streamdeck__get_executable_actions
  • streamdeck__execute_action
• Current action list is empty because no safe actions have been added to the Stream Deck MCP Actions profile yet.
• MCP does not expose full profile-authoring operations, so profile/buttons/folders/icons are not created through MCP.

Task

Create a documented MCP Actions Registry pilot for 5-7 safe AI-OS actions.

Recommended first actions:

• AIOS_HOME_JUDGE
• AIOS_HOME_REVISOR
• AIOS_HOME_SYNC
• AIOS_KB_SOURCE_TRUTH
• AIOS_LOCAL_AI_SAFETY
• AIOS_CODEX_ISSUE_TO_PR
• AIOS_AI_TREND

Required artifact

Create:

• StreamDeck/STREAMDECK_V2_8_MCP_ACTION_REGISTRY.md

The registry should include for each action:

• action_id
• title
• description
• owner project
• allowed input
• forbidden actions
• expected output
• safe_to_execute
• requires_confirmation
• smoke QA check
• residual risk

Manual setup note

If the Stream Deck MCP Actions profile must be edited manually, document exact manual steps.

Do not claim actions were created or executed unless observed through MCP.

Pilot QA

After manual action creation, verify through MCP if available:

• streamdeck__get_executable_actions lists the actions.
• Execute 1-2 safe actions only, preferably:
  • AIOS_HOME_JUDGE
  • AIOS_HOME_REVISOR
  • or AIOS_KB_SOURCE_TRUTH

Record:

• actions visible: yes / no
• actions executed: list
• observed result
• pass / revise / blocked
• residual risks

Safety constraints

Allowed:

• list MCP actions
• execute safe registered actions
• record evidence
• create/update documentation

Forbidden:

• deleting profiles
• overwriting v2.7 active profile
• enabling auto-send
• sending messages automatically
• auto-merge
• delete/publish/deploy
• secrets, credentials, private data, raw transcripts, runtime artifacts
• production automation
• autonomous retrieval
• vector DB
• semantic search
• embeddings
• production web UI workflow
• autonomous agents

Status rules

• v2.7 remains active.
• v2.8 remains candidate-only.
• Human acceptance is required before promotion.

Checks

Run:

• git diff --check
• python3 scripts/check_project_instructions_length.py
• python3 scripts/check_repo_public_safety.py
• python3 scripts/check_manifest_paths.py
• python3 scripts/check_knowledge_bundles.py

PR

Open or update a draft PR if files change.

Do not merge automatically.

[sergstack]

Reverified against current repo state on 2026-07-07.

Evidence already in repo:

• Merged PR [codex] Add StreamDeck v2.8 MCP setup and action registry #76 added StreamDeck v2.8 MCP setup/action-registry material.
• defines the requested 7 safe candidate actions: , , , , , , and .
• The registry documents action_id, title, description, owner project, allowed input, forbidden actions, expected output, safe_to_execute, requires_confirmation, smoke QA check, residual risk, manual setup steps, and safety constraints.
• records a later supervised MCP pilot where actions were visible and plus were executed; verdict: pass / candidate-only.
• keeps v2.7 active and v2.8 candidate-only, with manual migration/acceptance still required.

Current repo checks on the stacked verification branch pass:

• PASS ChatGPT/[AI OS]/PROJECT_INSTRUCTIONS.md chars=7066 limit=8000
  PASS ChatGPT/[Analytics]/PROJECT_INSTRUCTIONS.md chars=7153 limit=8000
  PASS ChatGPT/[Codex]/PROJECT_INSTRUCTIONS.md chars=6360 limit=8000
  PASS ChatGPT/[Inbox Router]/PROJECT_INSTRUCTIONS.md chars=4534 limit=8000
  PASS ChatGPT/[LLM]/PROJECT_INSTRUCTIONS.md chars=4122 limit=8000
  PASS ChatGPT/[Thinking]/PROJECT_INSTRUCTIONS.md chars=3433 limit=8000
  Checked PROJECT_INSTRUCTIONS.md files: 6
  Passed: 6
  Failed: 0
  Limit: 8000 characters
• Public safety check passed.
• Manifest JSON:
• PASS file exists: MANIFEST.json
• PASS JSON parses: MANIFEST.json
• PASS knowledge_files paths must exist: ChatGPT/[AI OS]/Knowledge/AI_OS_PROJECT_FILES_INDEX.md
• PASS knowledge_files paths must exist: ChatGPT/[AI OS]/Knowledge/AI_OS_WORKFLOW.md
• PASS knowledge_files paths must exist: ChatGPT/[AI OS]/Knowledge/ANTI_PATTERNS.md
• PASS knowledge_files paths must exist: ChatGPT/[AI OS]/Knowledge/GOVERNANCE_RULES.md
• PASS knowledge_files paths must exist: ChatGPT/[AI OS]/Knowledge/HANDOFF_PROTOCOL.md
• PASS knowledge_files paths must exist: ChatGPT/[AI OS]/Knowledge/KB_USAGE_RULES.md
• PASS knowledge_files paths must exist: ChatGPT/[AI OS]/Knowledge/PROJECT_ROUTING.md
• PASS knowledge_files paths must exist: ChatGPT/[AI OS]/Knowledge/SMOKE_QA_FOR_AI_OS.md
• PASS local_files paths must exist: AGENTS.md
• PASS local_files paths must exist: ARCHIVE_MAP.md
• PASS local_files paths must exist: COMMAND_SURFACE.md
• PASS local_files paths must exist: CONTEXT_PACK_STANDARD.md
• PASS local_files paths must exist: GOAL_PACKS.md
• PASS local_files paths must exist: GOAL_MODE.md
• PASS local_files paths must exist: SYNC_CONTRACT.md
• PASS local_files paths must exist: UPLOAD_GUIDE.md
• PASS local_files paths must exist: ChatGPT/[AI OS]/PROJECT_INSTRUCTIONS.md
• PASS local_files paths must exist: ChatGPT/[AI OS]/README.md
• PASS local_files paths must exist: .github/ISSUE_TEMPLATE/goal.md
• PASS local_files paths must exist: .github/ISSUE_TEMPLATE/codex-task.md
• PASS local_files paths must exist: scripts/sync_aios.py
• PASS validation_gates.project_instructions_chars_limit must equal 8000: MANIFEST.json
• PASS production_promotion must be present and equal no: MANIFEST.json

Manifest Markdown:

• PASS file exists: MANIFEST.md
• PASS current package/version must be referenced consistently: MANIFEST.md
• PASS must include PROJECT_INSTRUCTIONS.md <= 8000 characters rule: MANIFEST.md
• PASS must use canonical ChatGPT/[AI OS]/... paths: MANIFEST.md

Upload Guide:

• PASS file exists: UPLOAD_GUIDE.md
• PASS must use canonical Project Instructions repo path: UPLOAD_GUIDE.md
• PASS must use canonical Knowledge repo paths: UPLOAD_GUIDE.md
• PASS must identify Project Instructions paste target: UPLOAD_GUIDE.md
• PASS must identify Project Knowledge upload target: UPLOAD_GUIDE.md
• PASS must state only Knowledge files are uploaded to Project Knowledge: UPLOAD_GUIDE.md
• PASS must state README.md remains local or is not uploaded as Knowledge: UPLOAD_GUIDE.md
• PASS must include or reference <=8000 chars rule: UPLOAD_GUIDE.md

Repo Paths:

• PASS file exists: REPO_PATHS.md
• PASS must define canonical local path placeholders: REPO_PATHS.md
• PASS must define canonical local path placeholders: REPO_PATHS.md
• PASS canonical repo path must be listed and exist: ChatGPT/[AI OS]
• PASS canonical repo path must be listed and exist: ChatGPT/[Thinking]
• PASS canonical repo path must be listed and exist: ChatGPT/[Analytics]
• PASS canonical repo path must be listed and exist: ChatGPT/[LLM]
• PASS canonical repo path must be listed and exist: ChatGPT/[Codex]
• PASS canonical repo path must be listed and exist: ChatGPT/[Inbox Router]
• PASS canonical repo path must be listed and exist: Codex APP

Project Registry:

• PASS file exists: PROJECT_REGISTRY.md
• PASS ChatGPT project entry and PROJECT_INSTRUCTIONS.md path must exist: ChatGPT/[AI OS]/PROJECT_INSTRUCTIONS.md
• PASS Knowledge path exists for project using Knowledge: ChatGPT/[AI OS]/Knowledge
• PASS ChatGPT project entry and PROJECT_INSTRUCTIONS.md path must exist: ChatGPT/[Thinking]/PROJECT_INSTRUCTIONS.md
• PASS Knowledge path exists for project using Knowledge: ChatGPT/[Thinking]/Knowledge
• PASS ChatGPT project entry and PROJECT_INSTRUCTIONS.md path must exist: ChatGPT/[Analytics]/PROJECT_INSTRUCTIONS.md
• PASS Knowledge path exists for project using Knowledge: ChatGPT/[Analytics]/Knowledge
• PASS ChatGPT project entry and PROJECT_INSTRUCTIONS.md path must exist: ChatGPT/[LLM]/PROJECT_INSTRUCTIONS.md
• PASS Knowledge path exists for project using Knowledge: ChatGPT/[LLM]/Knowledge
• PASS ChatGPT project entry and PROJECT_INSTRUCTIONS.md path must exist: ChatGPT/[Codex]/PROJECT_INSTRUCTIONS.md
• PASS Knowledge path exists for project using Knowledge: ChatGPT/[Codex]/Knowledge
• PASS ChatGPT project entry and PROJECT_INSTRUCTIONS.md path must exist: ChatGPT/[Inbox Router]/PROJECT_INSTRUCTIONS.md
• PASS Knowledge path exists for project using Knowledge: ChatGPT/[Inbox Router]/Knowledge
• PASS Codex APP must be clearly marked as not a ChatGPT Project: PROJECT_REGISTRY.md

Master Status:

• PASS file exists: MASTER_STATUS.md
• PASS must include required validation gate: MASTER_STATUS.md
• PASS must include required validation gate: MASTER_STATUS.md
• PASS must include required validation gate: MASTER_STATUS.md
• PASS must include required validation gate: MASTER_STATUS.md
• PASS must include required validation gate: MASTER_STATUS.md
• PASS must include required validation gate: MASTER_STATUS.md
• PASS must not say production_promotion: yes: MASTER_STATUS.md

Project Instructions Coverage:

• PASS expected PROJECT_INSTRUCTIONS.md must exist: ChatGPT/[AI OS]/PROJECT_INSTRUCTIONS.md
• PASS expected PROJECT_INSTRUCTIONS.md must exist: ChatGPT/[Analytics]/PROJECT_INSTRUCTIONS.md
• PASS expected PROJECT_INSTRUCTIONS.md must exist: ChatGPT/[Codex]/PROJECT_INSTRUCTIONS.md
• PASS expected PROJECT_INSTRUCTIONS.md must exist: ChatGPT/[Inbox Router]/PROJECT_INSTRUCTIONS.md
• PASS expected PROJECT_INSTRUCTIONS.md must exist: ChatGPT/[LLM]/PROJECT_INSTRUCTIONS.md
• PASS expected PROJECT_INSTRUCTIONS.md must exist: ChatGPT/[Thinking]/PROJECT_INSTRUCTIONS.md
• PASS expected PROJECT_INSTRUCTIONS.md count must be at least 6: PROJECT_INSTRUCTIONS.md

Legacy Path Drift:

• PASS legacy path variant must not appear in governance docs: README.md
• PASS legacy path variant must not appear in governance docs: README.md
• PASS legacy path variant must not appear in governance docs: README.md
• PASS legacy path variant must not appear in governance docs: README.md
• PASS legacy path variant must not appear in governance docs: MASTER_STATUS.md
• PASS legacy path variant must not appear in governance docs: MASTER_STATUS.md
• PASS legacy path variant must not appear in governance docs: MASTER_STATUS.md
• PASS legacy path variant must not appear in governance docs: MASTER_STATUS.md
• PASS legacy path variant must not appear in governance docs: PROJECT_REGISTRY.md
• PASS legacy path variant must not appear in governance docs: PROJECT_REGISTRY.md
• PASS legacy path variant must not appear in governance docs: PROJECT_REGISTRY.md
• PASS legacy path variant must not appear in governance docs: PROJECT_REGISTRY.md
• PASS legacy path variant must not appear in governance docs: REPO_PATHS.md
• PASS legacy path variant must not appear in governance docs: REPO_PATHS.md
• PASS legacy path variant must not appear in governance docs: REPO_PATHS.md
• PASS legacy path variant must not appear in governance docs: REPO_PATHS.md
• PASS legacy path variant must not appear in governance docs: MANIFEST.md
• PASS legacy path variant must not appear in governance docs: MANIFEST.md
• PASS legacy path variant must not appear in governance docs: MANIFEST.md
• PASS legacy path variant must not appear in governance docs: MANIFEST.md
• PASS legacy path variant must not appear in governance docs: MANIFEST.json
• PASS legacy path variant must not appear in governance docs: MANIFEST.json
• PASS legacy path variant must not appear in governance docs: MANIFEST.json
• PASS legacy path variant must not appear in governance docs: MANIFEST.json
• PASS legacy path variant must not appear in governance docs: ARCHIVE_MAP.md
• PASS legacy path variant must not appear in governance docs: ARCHIVE_MAP.md
• PASS legacy path variant must not appear in governance docs: ARCHIVE_MAP.md
• PASS legacy path variant must not appear in governance docs: ARCHIVE_MAP.md
• PASS legacy path variant must not appear in governance docs: UPLOAD_GUIDE.md
• PASS legacy path variant must not appear in governance docs: UPLOAD_GUIDE.md
• PASS legacy path variant must not appear in governance docs: UPLOAD_GUIDE.md
• PASS legacy path variant must not appear in governance docs: UPLOAD_GUIDE.md
• PASS legacy path variant must not appear in governance docs: CURRENT_STATUS.md
• PASS legacy path variant must not appear in governance docs: CURRENT_STATUS.md
• PASS legacy path variant must not appear in governance docs: CURRENT_STATUS.md
• PASS legacy path variant must not appear in governance docs: CURRENT_STATUS.md

Summary:

• checked: 112
• passed: 112
• failed: 0
• Knowledge Bundle Check

Project: [AI OS]

• bundle folder: pass
• upload list: pass
• required files: 6
• optional files: 0
• total upload files: 6 / 40
• source paths: pass
• forbidden content: pass

Project: [Thinking]

• bundle folder: pass
• upload list: pass
• required files: 3
• optional files: 0
• total upload files: 3 / 40
• source paths: pass
• forbidden content: pass

Project: [Analytics]

• bundle folder: pass
• upload list: pass
• required files: 6
• optional files: 1
• total upload files: 7 / 40
• source paths: pass
• forbidden content: pass

Project: [LLM]

• bundle folder: pass
• upload list: pass
• required files: 6
• optional files: 0
• total upload files: 6 / 40
• source paths: pass
• forbidden content: pass

Project: [Codex]

• bundle folder: pass
• upload list: pass
• required files: 6
• optional files: 0
• total upload files: 6 / 40
• source paths: pass
• forbidden content: pass

Project: [Inbox Router]

• bundle folder: pass
• upload list: pass
• required files: 2
• optional files: 0
• total upload files: 2 / 40
• source paths: pass
• forbidden content: pass

Summary:

• projects checked: 6
• bundles checked: 30
• upload files max: 7
• failed: 0
• PASS AGENTS.md:9: context scopes task packages away from default Goal Mode: In default Goal Mode, Sergey may give a broad goal instead of an atomic task package. Codex should inspect the repository, infer a bounded and reversible scope, create or use a non-main branch for repository changes, implement the smallest useful working version, run meaningful checks, fix in-scope failures once when safe, and report evidence, risks, rollback, and acceptance status.
  PASS AGENTS.md:11: context scopes task packages away from default Goal Mode: Atomic task packages remain available for advanced, high-risk, strict, or ultra-long work, but they are not the default user burden. Do not turn a clear implementation goal into an epic, roadmap, child issue tree, or approval package unless Sergey asks for planning, the work cannot fit in one bounded PR, or a hard approval gate is reached.
  PASS README.md:13: context scopes task packages away from default Goal Mode: Atomic task packages remain available as advanced/strict mode, but they are not the default user burden. GitHub is the live source of truth; ChatGPT Project Knowledge is a cached baseline for Project bootstrapping and formal sync.
  PASS README.md:70: context scopes task packages away from default Goal Mode: The Codex Goal Mode scan reports every remaining atomic-task-package wording in Codex-facing files and fails if any wording implies atomic task packages are required by default.
  PASS GOAL_MODE.md:13: context scopes task packages away from default Goal Mode: In default Goal Mode, the user gives a broad goal, not an atomic task package.
  PASS GOAL_MODE.md:33: context scopes task packages away from default Goal Mode: Atomic task packages remain available for strict, high-risk, or already-scoped work. They are an internal safety mechanism by default, not a required form Sergey must write for normal goals.
  PASS GOAL_PACKS.md:5: context scopes task packages away from default Goal Mode: In default Goal Mode, Goal Packs are not atomic task packages. Codex still compiles internal scope, checks, rollback, and acceptance criteria before editing.
  PASS COMMAND_SURFACE.md:29: context scopes task packages away from default Goal Mode: - Use strict task packages only when scope is already known or risk is high.
  PASS CONTEXT_PACK_STANDARD.md:49: context scopes task packages away from default Goal Mode: - the receiving project can act without asking Sergey to write an atomic task package.
  PASS ChatGPT/[AI OS]/PROJECT_INSTRUCTIONS.md:156: context scopes task packages away from default Goal Mode: Broad goals are valid inputs. If the user wants implementation, sync, workflow, or repository change, frame the goal and route it to [LLM] or [Codex] without requiring Sergey to write an atomic task package.
  PASS ChatGPT/[AI OS]/Knowledge/HANDOFF_PROTOCOL.md:39: context scopes task packages away from default Goal Mode: 4. [Codex] реализует через Goal Mode handoff или strict task package со scope, checks, rollback и acceptance.
  PASS ChatGPT/[AI OS]/Knowledge_Bundles/AIOS_04_GOAL_PACKS_AND_COMMAND_SURFACE.md:33: context scopes task packages away from default Goal Mode: In default Goal Mode, Goal Packs are not atomic task packages. Codex still compiles internal scope, checks, rollback, and acceptance criteria before editing.
  PASS ChatGPT/[AI OS]/Knowledge_Bundles/AIOS_04_GOAL_PACKS_AND_COMMAND_SURFACE.md:89: context scopes task packages away from default Goal Mode: - Use strict task packages only when scope is already known or risk is high.
  PASS ChatGPT/[AI OS]/Knowledge_Bundles/AIOS_04_GOAL_PACKS_AND_COMMAND_SURFACE.md:132: context scopes task packages away from default Goal Mode: A Context Pack is ready when the goal is clear, sources are named, facts and assumptions are separated, constraints and forbidden actions are visible, the expected output is specific, and the receiving project can act without asking Sergey to write an atomic task package.
  PASS ChatGPT/[AI OS]/Knowledge_Bundles/AIOS_03_HANDOFF_AND_SMOKE_QA.md:52: context scopes task packages away from default Goal Mode: 4. [Codex] реализует через Goal Mode handoff или strict task package со scope, checks, rollback и acceptance.
  PASS ChatGPT/[Codex]/PROJECT_INSTRUCTIONS.md:9: context scopes task packages away from default Goal Mode: Default Goal Mode: [Codex] принимает broad repo/workflow goals, сам inspect/infer bounded safe scope, затем делает smallest useful verified change. Strict task packages are only for high-risk, already-scoped, ultra-long, or explicitly requested work.
  PASS ChatGPT/[Codex]/Knowledge/PROJECT_CONTEXT.md:10: context scopes task packages away from default Goal Mode: - Atomic task packages only for strict, high-risk, already-scoped, or ultra-long work.
  PASS ChatGPT/[Codex]/Knowledge/AGENTS.md:5: context scopes task packages away from default Goal Mode: Codex is an implementation agent. In Goal Mode it accepts broad goals, inspects the repository, infers bounded safe scope, makes the smallest useful scoped change, runs checks, and reports results. Strict task packages remain available for high-risk, already-scoped, or ultra-long work.
  PASS ChatGPT/[Codex]/Knowledge_Bundles/CODEX_05_AGENT_REFERENCES.md:33: context scopes task packages away from default Goal Mode: Codex is an implementation agent. In Goal Mode it accepts broad goals, inspects the repository, infers bounded safe scope, makes the smallest useful scoped change, runs checks, and reports results. Strict task packages remain available for high-risk, already-scoped, or ultra-long work.
  PASS ChatGPT/[Codex]/Knowledge_Bundles/CODEX_05_AGENT_REFERENCES.md:177: context scopes task packages away from default Goal Mode: - Atomic task packages only for strict, high-risk, already-scoped, or ultra-long work.
  Codex Goal Mode atomic-default occurrences checked: 20
  Failed: 0
• ........... [100%]
  11 passed in 0.42s

Remaining manual blocker:

• The full 7-action set still needs manual Stream Deck profile setup verification and broader live MCP smoke execution. The repo should not claim full promotion until that evidence is recorded.

Recommendation: close this issue if the accepted scope is registry + initial supervised MCP pilot. If the intended scope is full live verification of all 7 actions, keep it open as a manual StreamDeck follow-up; no additional repo artifact is currently needed.

[sergstack]

Correction to the previous comment: shell expanded markdown code spans in that note. Clean evidence summary below.

Reverified against current repo state on 2026-07-07.

Evidence already in repo:

• Merged PR [codex] Add StreamDeck v2.8 MCP setup and action registry #76 added StreamDeck v2.8 MCP setup and action-registry material.
• StreamDeck/STREAMDECK_V2_8_MCP_ACTION_REGISTRY.md defines the requested 7 safe candidate actions: AIOS_HOME_JUDGE, AIOS_HOME_REVISOR, AIOS_HOME_SYNC, AIOS_KB_SOURCE_TRUTH, AIOS_LOCAL_AI_SAFETY, AIOS_CODEX_ISSUE_TO_PR, and AIOS_AI_TREND.
• The registry documents action_id, title, description, owner project, allowed input, forbidden actions, expected output, safe_to_execute, requires_confirmation, smoke QA check, residual risk, manual setup steps, and safety constraints.
• StreamDeck/STREAMDECK_V2_8_MCP_ACTIONS_PILOT.md records a later supervised MCP pilot where actions were visible and AIOS_HOME_JUDGE plus AIOS_HOME_REVISOR were executed. Verdict: pass / candidate-only.
• StreamDeck/README.md keeps v2.7 active and v2.8 candidate-only, with manual migration/acceptance still required.

Checks observed on the current stacked verification branch:

• project instruction length: pass
• public safety: pass
• manifest paths: pass
• knowledge bundles: pass
• Codex Goal Mode defaults: pass
• pytest tests/: 11 passed
• git diff --check: pass

Remaining manual blocker:

• The full 7-action set still needs manual Stream Deck MCP Actions profile setup verification and broader live MCP smoke execution. The repo should not claim full promotion until that evidence is recorded.

Recommendation: close this issue if the accepted scope is registry plus initial supervised MCP pilot. If the intended scope is full live verification of all 7 actions, keep it open as a manual StreamDeck follow-up. No additional repo artifact is currently needed.

[sergstack]

Closing as complete for the accepted scope: StreamDeck v2.8 MCP action registry plus initial supervised MCP pilot are documented in repo evidence. Full manual verification of all 7 actions remains a future manual follow-up if needed; v2.8 stays candidate-only and production promotion remains no.