Skip to content

feat(t27os): orchestrator v1 and lane commit defaults (Refs #13260) - #13523

Merged
cursor[bot] merged 3 commits into
masterfrom
claude/godmode-orchestrator-v1
Nov 9, 2026
Merged

cursor[bot] merged 3 commits into
masterfrom
claude/godmode-orchestrator-v1

Conversation

@gHashTag

@gHashTag gHashTag commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Pull Request Checklist

  • PR title follows semantic convention: feat(scope): description, fix(scope): description, etc.
  • PR body includes Closes #N reference (see Issue Gate)
  • Tests added/updated: ./scripts/tri test passes locally
  • Specs changed → seals refreshed: ./scripts/tri seal specs/path/to/module.t27 --save

Description

T27 OS orchestrator v1. A lane may commit and push its own branch. Merge, publication, host files, and the window shell stay gated. Refs #13260. This does not close that issue.

Changes

  • specs/t27os/orchestrator.t27 — allowed acts and the git-tri predicates
  • specs/t27os/dashboard.t27 — shown-byte to blocked, working, or idle
  • specs/t27os/queue.t27 — slot wait, assigned lane via oc_branch_ok
  • specs/t27os/blockers.t27 — internal versus external, gated act via oc_needs_owner
  • specs/t27os/reports.t27 — five report fields, pull request via oc_pr_ok
  • .claude/skills/git-tri-defaults/SKILL.md — the same rules, pointing at the spec

Testing

Typecheck of these specs was reported OK on the source lane. Test bodies were not run. Seals were not refreshed.

Documentation

The skill points at specs/t27os/orchestrator.t27. The spec wins if they disagree.

Review Notes

Reviewer boundary: specs/OWNERS.md, primary T-Queen. specs/t27os/ has no nested OWNERS file. specs/automation/t27_plan.t27 is not in this pull request: the current plan calls the agent network, so it lands in the stacked follow-up. Draft. Do not merge from this pull request. The window shell stays closed.


φ² + 1/φ² = 3 | TRINITY


Note

Medium Risk
Introduces the permission model agents are expected to follow for git operations and owner-gated acts, though enforcement lives in callers that adopt these specs.

Overview
Adds T27 OS orchestrator v1 as checked law in orchestrator.t27: commit, push, and PR are allowed by default on an agent’s own lane; merge, publication, host files, mail, paid calls, shell/window, and similar acts require owner permission via oc_needs_owner and the oc_*_ok predicates.

Dashboard, queue, blockers, and reports specs are aligned to that model: dashboard maps the PTY shown byte to blocked/working/idle; queue slot-wait plus assigned-lane checks call oc_branch_ok; blockers split internal vs external and treat gated acts as internal blockers; reports require five fields before oc_pr_ok can allow opening a PR.

The git-tri-defaults skill documents the same commit → branch → push → PR flow and points at orchestrator.t27 as authoritative.

Reviewed by Cursor Bugbot for commit f1c940e. Bugbot is set up for automated code reviews on this repo. Configure here.

A lane may commit and push. Merge and the window shell stay gated. Refs #13260.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-09 18:25:29 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 42
PRs with All Checks Green 8
READY 3
FAILING 42
PENDING 0
NO CHECKS YET 0

These columns do not partition: 3 + 42 + 0 + 0 = 45, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=b882be1e4933 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

Twenty-seven domains, one owner per spec, no command body moved. Refs #13260.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Dmitrii Vasilev <gHashTag@users.noreply.github.com>
This was referenced Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-09 21:50:03 UTC

Summary

Status Count
Total Open PRs 44
PRs with Failing Checks 42
PRs with All Checks Green 2
READY 0
FAILING 42
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 42 + 0 + 0 = 42, and there are 44 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=b882be1e4933 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants