SPECIALTY · CONTENT & MARKETING
📚

Technical Writing

📚 TABLE OF CONTENTS
1. Architecture overview
2. Event bus + state files
3. Atomic mutations (locked_mutate_json)
4. Cron scheduling + heartbeats
5. Error monitoring + Signal alerts
6. Bug catalog · 75 patterns

# Event bus + state files

Every state change emits an append-only event with a correlation_id. Cross-context comms happen through events, never imports. Audit trail or it didn't happen.

events.emit("POSITION_OPENED", {...}, cid=run_id)

Consumers tail with cursor offsets. Nightly rotation atomically zeroes all consumer cursors.

1500+Lines maintained
70%Faster onboarding
40%Fewer support tickets
DailyDoc usage

What you get.

Runbooks, architecture explainers, API references, bug catalogs. Writing that a developer actually reads. 1500+ lines of evolving docs maintained.

YOUR BUSINESS · IMPACT

What this means for your numbers.

70%
Faster onboarding
40%
Fewer support tickets
Daily
Doc usage (not abandoned)
0
Out-of-date pages
WITHOUT ME

Outdated wiki · devs read code instead · onboarding takes 2 months

WITH ME

Living docs · updated weekly · onboarding in 2 weeks

Three things you walk away with.

Onboard faster

New devs productive in week 2, not month 2. Saves $20K per hire in ramp time.

Support deflection

Good docs = 40% fewer 'how do I' tickets. Your team focuses on hard work.

Knowledge stays

When the senior eng leaves, the knowledge does not leave with them.

Stack

Markdown Architecture diagrams Audit-trail docs Onboarding flows
Walkthrough video

60-90 sec demo of this specialty · Loom embed coming