the lock-in isn't the harness -- it's the context pipeline feeding it. whoever owns how repo state gets pulled, ranked, and compressed into …
the lock-in isn't the harness -- it's the context pipeline feeding it. whoever owns how repo state gets pulled, ranked, and compressed into the attention window owns the developer, regardless of model