A platform bridge is an interface with a lifetime problem
Permissions, biometrics and share sheets all need something shared code does not have: a host that outlives the call.
architecture
70 posts
kotlinx.serialization is compile-time, which is why your polymorphism fails at runtime
No reflection on Native, so the serializer is generated. Sealed hierarchies work; open polymorphism needs a module you register by hand.
A ceiling in a conditional is one someone deletes
A budget expressed as a value can be read, derived from and audited. Buried in a conditional it can only be obeyed or removed, and it gets removed.
Loading every rule up front is how none of them apply
An always-loaded rulebook competes with itself for attention. Matching the tool target and injecting only what fires turns 588 rules into the twelve that apply.
Editing the generated thing is how the spec stops meaning anything
A change implemented directly in source skips the spec, so every report downstream is computed without it. The feature works and nothing can see it.
Every generated file should say what made it
A generated artifact carries no record of how it was made once the process ends. A provenance sidecar makes which-path-produced-this answerable by grep.
A generator given the wrong context does not stop
Scoping a context pack by project type saved 8.2% per subagent, not the 40% I guessed. The real risk is a thin pack: a missing surface makes a generator invent.
Two places that both think they are the truth
A durable source of truth and an in-memory one give the same answers until a process dies. Deciding which is authoritative is a design act, not a default.
The export engine that exported nothing
A stub is not an empty function. It returns plausible values, satisfies its interface and does no work, which is why emptiness checks never find it.
A retry queue with nothing to run it is a graveyard
A failed-sync flag is not a retry mechanism. Three parts are needed: a connectivity signal, an enumeration of what failed, and backoff with a ceiling.
The corpus your generator reads is production code
The corpus a generator reads is as load-bearing as the code it emits. A hand-edit to it has no provenance and is dropped by the next re-sync.
Last write wins is a decision, not a default
When two writes reach one record and no code decides between them, the policy is whichever ran last. Name the resolver so the choice becomes reviewable.