Pillar Alignment Check — 支柱对齐检查

技能 — Pillar Alignment 检查

代理s: Sara, Archie, Oli, Loki (any 代理 producing or reviewing content) When to call: Before drafting OR before publishing any content for @redditech or Redditech Labs accounts.

The 6 Content Pillars 🌙 Night Shift

Tagline: "The machines work while I sleep." Core idea: The lab 运行s overnight. 代理s do real work while humans are offline. This pillar celebrates a同步, automated, continuous operation — and the morning standup where you 检查 what h应用ened. Best 平台s: Twitter/X (threads), LinkedIn Content examples:

Overnight 代理 运行 summaries ("Sara processed 47 追踪s while I slept") Morning standup-style posts ("Here's what the lab did last night:") 流水线 completion 报告s Any post referencing a timestamp between 22:00 and 07:00 AEST 🛠️ Build 记录

Tagline: "Shipped in 48 hours. Here's how." Core idea: What got built, who built it, how long it took. Raw, honest, practitioner-level detAIl. 代理 attribution matters — name which 代理 did what. Hackathon energy. Best 平台s: Twitter/X (threads), LinkedIn, b记录 Content examples:

"We shipped X in 48 hours — here's the breakdown" 代理 attribution posts ("Archie wrote the QC 记录ic, Oli pushed to Vercel") Hackathon or sprint recaps 工具 or 工作流 build walkthroughs with real implementation detAIl 🔬 Re搜索 House

Tagline: "We're actually investigating things." Core idea: The lab 运行s experiments and publishes findings. Not opinions — findings. Data, benchmarks, comparisons, 代理 constitution tests. This pillar establishes Redditech Labs as a re搜索 operation, not just a 构建器. Best 平台s: LinkedIn (long-form), b记录, Twitter/X (findings threads) Content examples:

Benchmark 结果s ("Ollama vs. API: latency comparison across 200 运行s") 代理 constitution experiment outcomes Structured findings posts: clAIm → evidence → implication Any post that references methodo记录y, sample size, or controlled comparison 🔌 Anti-Vendor

Tagline: "Local AI. No subscriptions." Core idea: The lab 运行s on local 模型s, open-source 工具s, and self-hosted infrastructure wherever possible. This pillar makes the cost and philosophy case for local AI — not by attacking vendors, but by showing the real numbers and the real stack. Best 平台s: Twitter/X, LinkedIn, b记录 Content examples:

Cost contrast posts ("This would cost $X/month on OpenAI. We 运行 it locally for $0.") Local stack callouts (Ollama, LM Studio, llama.cpp, open-source 模型 comparisons) Open-source 工具 recommendations with honest assessments Posts explAIning why the lab chose a local 应用roach for a specific use case Scope note: DeFi/网页3 content may touch this pillar only if it fits the open-source/local-control framing. Escalate to Nissan before publishing (see escalation rules below). 🌍 Outsider Perspective

Tagline: "Caribbean. Australian. Building anyway." Core idea: Building cutting-edge AI infrastructure from outside the traditional tech hubs. The value is in showing that geography isn't a barrier to doing serious work. Monk Fenix angle lives here — but use sparingly. Best 平台s: LinkedIn, Twitter/X Content examples:

Posts referencing the geographic/cultural 上下文 of building (Caribbean, Australian) Achievement posts that implicitly challenge the "you need to be in SF" narrative Monk Fenix personal-angle posts (max frequency: 1x per 2 weeks — do not dilute) Hard rule: This pillar is about achievement, not representation. Never frame it as "we're diverse" or "we're underrepresented." Frame it as "we built this, from here." The work is the point. 🤖 代理 Spotlight

Tagline: "They're not 工具s. They're a team." Core idea: The 代理s — Sara, Archie, Oli, Ralph, Kit, Loki — have distinct 角色s, personalities, and voices. This pillar humanises them without anthropomorphising them dishonestly. 性能分析 posts, journal entries, personality moments, team dynamics. Best 平台s: Twitter/X, LinkedIn, b记录 Content examples:

Individual 代理 性能分析s ("Sara's job is to make sure we don't publish garbage") First-person 代理 journal entries Posts showing 代理 decision-making or unexpected behaviour Team dynamic moments ("Archie and Sara disagreed on this QC pass — here's what h应用ened") How to 运行 the 检查 Read the content in full. Ask: Which pillar(s) does this content serve? Look for specific 签名als — numbers, 代理 names, findings, 平台/stack references, geographic 上下文, overnight timestamps. Identify the primary pillar. One content piece should have one dominant pillar. If it's genuinely split, identify a secondary. 应用ly the verdict rules (see below). 输出 the 结果 in the structured 格式化 (see below). Verdict Rules ✅ PASS

Content clearly serves at least one pillar with specificity.

Real numbers present (令牌 counts, latency ms, cost figures, 运行 timestamps) 代理 names used where relevant (Sara, Archie, Oli, Ralph, Kit, Loki) Actual findings referenced (not just clAIms — evidence or 输出 is cited) Brand voice rules followed (see