Repository navigation
feat(t27os): blog video brand contract - #13526
Conversation
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>
Co-authored-by: Dmitrii Vasilev <gHashTag@users.noreply.github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ 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 ""; | ||
| } |
There was a problem hiding this comment.
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)
Reviewed by Cursor Bugbot for commit 69fd2c0. Configure here.


Pull Request Checklist
feat(scope): descriptionCloses #Nreference. 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, becausedocs/promotion/content-calendar.mdwould be a newdocs/top level under Article DOCS-TREE, and this branch does not publish.t27c test-reporton the three files passed. The full./scripts/tri testcorpus was not run.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)fromspecs/t27f/vf_theme.t27. The wide frame is the YouTube moving format fromspecs/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_menuRGB_WHITE). Screens use only the public builders inspecs/t27f/ui_kit.t27.window_shell()isblockedandGLASS_OPENis false.glass_window.t27is 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 shellspecs/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
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_capassumes 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 unblockglass_window.t27.φ² + 1/φ² = 3 | TRINITY
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.