🏛️ Autonomous Team Governance Standard · 100% Deterministic & Zero-Meeting

Workforce Governance Architecture Specification

The complete, production-verified operating manual for setting up, balancing, and executing autonomous workforce governance across R&D Engineering and Sales.

💻 R&D Engineering Workforce Architecture

Operational standard for senior software architects, frontend/backend engineers, and technical leads (Charles Liu & Romit Bhingradiya Standard).

7 Outcome Pillars · 8.0h Daily Budget · Zero Synthetic Overhead
1️⃣
How to Set Pillar 1 (Set 1: Outcome Pillars, 100% Fixed Shared Weight)
Permanent architectural outcome dimensions for engineering teams

Pillar 1 represents high-level engineering deliverables and production reliability. The 100% weight is permanently partitioned across 7 core outcome dimensions. Each dimension has an explicit, automated evaluation rule:

Code Performance 30%
Evaluates daily code contribution volume, build integrity, and clean compilation.
Rule: Git Commits ≥ 2 & clean build → 100%
Target Met 20%
Dynamic link reflecting the real-time completion of assigned daily actions in Pillar 2.
Rule: (Verified ÷ Assigned) × 20 pts
Production Reliability 15%
Production uptime, zero unhandled Linode/Sentry alerts, and container health checks.
Rule: Zero unhandled P0/P1 alerts → 100%
AI Progress Match 10%
Consistency score between developer work diary claims and AI-Helper live telemetry.
Rule: Match Consistency ≥ 80% → 100%
Time Meets Required 10%
Time tracking adherence comparing actual logged execution time against budgeted estimates.
Rule: Compliance Band 85% ~ 125% → 100%
Reviews / Knowledge 10%
Architectural handover specs (task-XXX-handover.md), code reviews, and PR audit quality.
Rule: Handover documented & merged → 100%
Schedule Meets Required 5%
On-time milestone delivery against sprint deadlines and product roadmap targets.
Rule: Milestone on or ahead of time → 100%
Key Architectural Principle: Pillar 1 weights are fixed and shared across the team. Individual engineers do not modify these percentages; instead, their daily performance scores within these 7 dimensions are driven automatically by Pillar 2 execution and live system telemetry.
2️⃣
How to Set Pillar 2 (Set 2: Daily Process, Dynamic 8.0h / 100 Pts Budget)
Atomic task breakdown, balanced daily budget, and two-way verification contracts

Pillar 2 governs daily tactical execution. Rather than managing vague, sprawling tasks, engineers decompose their primary daily deliverable into 4 to 5 atomic action cards under a strict mathematical budget:

Governance Rule Standard Specification Enforcement Mechanism
Strict 8.0h Budget The sum of allocated hours across all daily cards must equal exactly 8.0 hours (e.g. 4 cards × 2.0h or 2h + 2h + 2h + 1h + 1h). AI-Helper rejects budgets < 8.0h or > 8.0h, preventing ghost hours and artificial overages.
100 Pts Balance Points are distributed proportionally based on budgeted hours (2.0h = 25 pts, 1.0h = 12.5 pts), totaling 100 pts. Guarantees that finishing all daily tasks yields exactly 100 / 100 points.
Two-Way Contract Every card must define both What Should Do (implementation blueprint) and How to Measure (verification probe). Eliminates subjective disputes; verification runs Track A deterministic probes.
Rolled-Over Protocol Tasks uncompleted at day's end are automatically tagged [ROLLED-OVER] and carried into tomorrow's Sheet 1. Ensures zero silent task abandonment while transparently tracking carry-over penalties.
// Example: Charles Liu 2026-11-18 Telegram Gateway Decomposition (8.0h / 100 Pts) Card 1: Telegram Bot Gateway Setup → 2.0h | 25 pts | Probe: curl /api/telegram/health == 200 Card 2: Inbound Payload Normalization → 2.0h | 25 pts | Probe: Telegram → Unified Msg Schema test PASS Card 3: Unibox Live Stream & SSE Broadcast → 2.0h | 25 pts | Probe: <350ms SSE stream latency verified Card 4: 2-Way Reply Routing & Telemetry Sync → 2.0h | 25 pts | Probe: UI reply roundtrip reaches Telegram client Total Balanced: 4 Tasks × 2.0h = 8.0 Hours Logged | 100 / 100 Target Points
3️⃣
KPI Calculation & Contribution Architecture (Pillar 2 → Pillar 1)
Dual Donut mechanism: How daily process execution moves project accumulation to 100% DONE

The system visualizes workforce performance through a Dual Donut Architecture. Pillar 2 does not stand alone; it serves as the kinetic engine feeding Pillar 1:

Initial State (Start of Day) 45 / 100
Code Performance (30%) and Production Reliability (15%) are satisfied by morning health checks, yielding 45 pts. However, Target Met (0%), AI Match (0%), Time (0%), and Schedule (0%) are pending verification.
Status: Needs Attention (45/100)
Final State (All Tasks Verified) 100 / 100
As the 4 Pillar 2 tasks pass Track A verification, Target Met increases to 20/20, AI Match confirms 10/10, Time achieves 10/10, and Schedule adds 5/5. Pillar 1 achieves 100% DONE.
Status: Grade A+ (100/100 DONE)
// Mathematical Formula for Target Met Contribution: Target Met Pts = (Σ Verified Completed Tasks ÷ Total Assigned Tasks) × 20 pts Initial: (0 ÷ 4) × 20 = 0.0 pts → Pillar 1 Score = 30 (Code) + 15 (Rel) + 0 = 45 / 100 Task 1 Done: (1 ÷ 4) × 20 = 5.0 pts → Pillar 1 Score = 45 + 5 = 50 / 100 Task 2 Done: (2 ÷ 4) × 20 = 10.0 pts → Pillar 1 Score = 50 + 5 = 55 / 100 Task 3 Done: (3 ÷ 4) × 20 = 15.0 pts → Pillar 1 Score = 55 + 5 = 60 / 100 All 4 Done + Telemetry PASS: (4 ÷ 4) × 20 = 20 pts + AI (10) + Time (10) + Sched (5) = 100 / 100 DONE (100%)
4️⃣
How to Set Up the Work Scheduler (Excel 5-Sheet View)
Complete runbook for the 5 interactive sheets and execution toolbar

The Work Scheduler organizes team planning into 5 discrete, interconnected sheets accessible via the Workforce Scheduler (Excel 5-Sheet View) tab:

Sheet Name Role & Content Operational Lifecycle
(1) To do list Active 8.0h / 100 pts execution queue for today. Contains task title, budgeted hours, priority, and verification probes. Populated each morning from roadmap epics; editable via inline table or Excel import.
(2) done Archive of completed deliverables verified by Track A probes with Git commit hashes and CI tokens. Tasks move here automatically once verified; permanent record for performance reviews.
(3) Roll over Tasks deferred due to upstream blockers or cross-day complexity. Includes blocker reasons and unlock dates. Unlocks transparent accountability; prevents silent dropping of delayed features.
(4) new assignment Architectural backlog pool containing unassigned feature specs, technical debt, and future epics. Curated by engineering leads and Steve Hung; feeds future To-Do lists.
(5) Video Video evidence repository with Loom screencasts, UI flow recordings, and architectural walkthroughs. Mandatory for visual UI deliverables to satisfy Track B human usability signoff.
Interactive Action Toolbar:
• Edit in Excel Form: Opens modal for structured bulk editing with validation.
• + Add Task (Excel Form): Appends a new item into Sheet 1 while auto-rebalancing total hours.
• Download .xlsx: Generates a complete 5-sheet Excel workbook with native styling and formulas.
• Upload Edited Excel: Ingests modified spreadsheets, validates 8.0h budget, and live-syncs the database.
5️⃣
How AI Measures Engineering Capability & Slices Real-Time Consuming
Automated telemetry probes and L1~L4 delivery maturity classification

Rather than relying on self-reported estimates or subjective opinions, the AI-Helper continuously tracks 5 deterministic telemetry metrics to quantify engineering capability:

Throughput
PRs merged and production deployments executed per unit of time without rollbacks.
Cycle Time
Elapsed hours from first commit on a feature branch to production release.
Lead Time
Total duration from task assignment in Sheet 1 to verified production closure.
Velocity
Net story points delivered against architectural complexity benchmarks.
7-Day Deficits
Post-release bug escapes, regression count, and MTTR on production incidents.

L1~L4 Delivery Maturity Levels & Standard Time Slices

Level Standard Time Budget Deliverable Scope & Verification Criteria
L1: Declared 1.0 hour Single config modification, environment variable update, or isolated documentation commit.
L2: Handshake 1.2 ~ 1.6 hours API endpoint stub, schema validation, and database migration script with mock response.
L3: Functional 1.6 ~ 2.0 hours Complete backend business logic, integration test suite passing, and error handling.
L4: Accepted 2.0 ~ 3.2 hours End-to-end user flow, Track A automated probe pass, live staging verification, and supervisor signoff.
← Return to Workforce Interactive Introduction Start 14-Day Free Trial →