Skip to content

feat(t27os): blog video brand contract - #13526

Merged
gHashTag merged 2 commits into
masterfrom
cursor/video-brand-cloud-c9ec
Nov 17, 2026
Merged

gHashTag merged 2 commits into
masterfrom
cursor/video-brand-cloud-c9ec

Conversation

@gHashTag

@gHashTag gHashTag commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Pull Request Checklist

  • PR title follows semantic convention: feat(scope): description
  • PR body includes Closes #N reference. Not used: see [M0-04] Content calendar (10-day cycle + weekly cadence) #13477 and [EPIC] T27_PROMOTION_KERNEL_V5 #13473. The calendar spec does not finish the issue, because docs/promotion/content-calendar.md would be a new docs/ top level under Article DOCS-TREE, and this branch does not publish.
  • Tests added in the specs. Focused t27c test-report on the three files passed. The full ./scripts/tri test corpus was not run.
  • Seals not refreshed. New specs are unsealed (neutral for claw/t27f).

Description

Reusable contract for every new T27 OS blog video, plus the 10-day content calendar as a spec that cannot publish.

The video files were absent on master. The ground color is vf_fill(THEME_DARK, VF_NONE) from specs/t27f/vf_theme.t27. The wide frame is the YouTube moving format from specs/claw/social_visuals.t27 (factory 16:9). A 9:16 cut is returned only when the caller asks. The accent is the white Trinity triangle (petal_menu RGB_WHITE). Screens use only the public builders in specs/t27f/ui_kit.t27. window_shell() is blocked and GLASS_OPEN is false. glass_window.t27 is not edited. Formulas are not restated.

Nothing was posted, scheduled, or sent to X, YouTube, Instagram, Telegram, email, or any other live network. This PR is not merged.

Changes

  • specs/t27os/video_brand.t27 — frame, ground, type, end card (@t27_lang, CTA), kit allowlist, blocked shell
  • specs/t27os/video_templates.t27 — title, one idea, end card (T27OS_VIDEO_BRAND_V1)
  • specs/t27os/content_calendar.t27 — 10-day cycle, weekly cadence, pillar tags, publish forced off (see [M0-04] Content calendar (10-day cycle + weekly cadence) #13477)

Testing

./target/debug/t27c typecheck specs/t27os/video_brand.t27
./target/debug/t27c typecheck specs/t27os/video_templates.t27
./target/debug/t27c typecheck specs/t27os/content_calendar.t27
./target/debug/t27c test-report specs/t27os/video_brand.t27
./target/debug/t27c test-report specs/t27os/video_templates.t27
./target/debug/t27c test-report specs/t27os/content_calendar.t27

Typecheck: OK, 0 errors, 0 warnings on each file.
test-report: video_brand 6/6, video_templates 5/5, content_calendar 3/3, vacuous 0. Invariants proved at compile time. Zig 0.16.0. No corpus suite.

Documentation

No new docs/ directory. The cycle law is the spec.

Review Notes

line_cap assumes a half-em advance; that assumption is stated in the spec. The shell flags are constants in the brand spec. They do not wire or unblock glass_window.t27.


φ² + 1/φ² = 3 | TRINITY

Open in Web Open in Cursor 

Note

Low Risk
Adds declarative specs with publish flags forced off and blocked-shell invariants; no runtime networking, auth, or live publish paths.

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

The reusable T27 OS blog-video law reads the existing dark theme, the
factory frame sizes and the UI kit builders. The window shell stays
blocked. A 10-day content calendar records the cycle and refuses to publish.

Co-authored-by: Dmitrii Vasilev <gHashTag@users.noreply.github.com>
@cursor
cursor Bot enabled auto-merge (squash) November 9, 2026 19:50
Co-authored-by: Dmitrii Vasilev <gHashTag@users.noreply.github.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 69fd2c0. Configure here.

if p == PILLAR_METRIC { return "metric"; }
if p == PILLAR_PATH { return "path"; }
return "";
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Calendar contradicts existing cycle law

Medium Severity

content_calendar.t27 presents itself as the #13477 cycle law, but pillar_index / pillar_tag assign six asset-field tags via day % 6. The executable law in promotion_kernel.t27 (day_pillar) already maps the same ten days to five content pillars two days each (proof, artifact, course, github, cta), and docs/promotion/content-calendar.md already exists. Callers of the new spec therefore get a different day-to-pillar calendar than the kernel, including only one metric day and one path day per cycle.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 69fd2c0. Configure here.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-09 20:12:41 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 40
PRs with All Checks Green 10
READY 0
FAILING 40
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 40 + 0 + 0 = 40, 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).

This was referenced Nov 15, 2026
@gHashTag
gHashTag merged commit a7646e8 into master Nov 17, 2026
33 of 44 checks passed
@gHashTag
gHashTag deleted the cursor/video-brand-cloud-c9ec branch November 17, 2026 10:53
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