billwear.github.io · Masque Protocol

Deep Blocks & Artifact Library

Schedule depth. Ship proof. Patterns for starting, protecting focus, and producing manager-visible artifacts.

Promise: One protected block → one artifact you can point to.

Deep work matters, but in ESTJ worlds, artifacts are the currency. This module gives you a planner, environment setup, 5-minute starting scripts, and artifact patterns so every block produces something legible: a brief, diagram, PR, decision note, or status delta.

Block Planner

Define the block

Block etiquette

Environment Setup

Room

Apps

Body

“Start in 5” Scripts

Writer
1) Open brief.md
2) Write headline & outcome line
3) Bullet 3 beats → expand first beat.
Engineer
1) Open PR draft
2) Write “Intent / Approach / Risks”
3) Stub tests → write first test → make it pass.
Researcher
1) Open notes
2) Write question & success criteria
3) Collect 5 sources → extract 5 quotes.

Artifact Patterns

One-Page Brief
Title
Outcome (one line)
Context (3 bullets)
Options (A/B)
Recommendation (why)
Next Step (owner · date)
Decision Note
Decision: __________
Why: short rationale
Risks: top 1–2 with owners
Next: concrete step + date
Status Delta
Was: (yesterday)
Now: (today)
Delta: (what moved)
Blockers: (who can unblock)
Next: (by when)
PR Message
Intent: what this does
Approach: how
Evidence: tests/bench/run
Risks: where to poke
Next: review asks
Diagram (words-first)
Nodes: A, B, C
Edges: A→B (why), B→C (why)
Invariants: must hold true
Failure paths: and mitigations

Cadence & Calendar

Troubleshooting

  • Can’t start: Use a “Start in 2” (open file → write header → first sentence/test).
  • Interruptions: Calendar hard block + DND + status message. If broken, reschedule—don’t smear.
  • No artifact: You did too much. Shrink scope; ship a brief/decision note first.

Templates

Block Card
Time: ___–___
Outcome: _______
Artifact: _______
Next: _______
Standup Delta
Done / Doing / Risks / Ask
Diagram Stencil
Nodes | Edges | Invariants | Failures