Machine-readable page content
Canonical: https://semiotic.nteract.io/examples/merge-pressure
Merge Pressure
Review queues under AI throughputAI can increase code production without increasing review capacity. Each pull request is a bundle: how much code it carries, what risks ride with it, and what happens when CI sends it back. Only merges count toward shipping the feature.
Feature thresholdUnique merged PRs contribute their code points once.18 merged points
PR coreCircle area grows with code points; arrivals are staggered by the scenario.
Negative traitSquare satellites remain attached until AI or human review transforms or removes them.
Shared serviceHuman review is one shared queue—PRs wait their turn.
FeatureOnly merged PR work fills the feature. Reviewing alone does not.
Coding throttles the system: 5 PRs carry 20 code points. Incoming work is 3.4 points per second against 5 review points per second. 0 of 18 Feature points have merged.
Event tape
What actually changed
Stream startingPR compounds will arrive on their own project-local clocks. Reusable mechanics
Entity, service, transition, aggregate.
The page supplies domain data and policies. GauntletChart now owns staggered local timelines, core-only capacity service, occurrence-preserving property changes, and an ordered event tape. The process recipe owns weighted group completion, so a Feature can be any threshold of uniquely completed member value.
compound entityOne semantic PR is a core plus repeated negative-property occurrences.
shared capacityA gate processes root entities by work units and re-arms only after a real exit.
weighted groupMerged PR values accumulate once toward a generic threshold outcome.