The Context Gap
Context resets every time zones shift. London wakes up and spends 2 hours figuring out what NY did.
PR Limbo
You push a PR at 5 PM. It sits for 14 hours because the reviewer had one small question they couldn't ask.
"Just in Case"
Engineers staying online until 9 PM "just in case" someone on the West Coast has a question.
Dead Docs
Async docs that no one reads and go stale the moment they are written.
Engineering Context Transfer
We replace "being online" with "declared state".
Highlights:
- Auth API refactor complete.
- PR #482 ready for review.
Blockers:
- Waiting on Ops for new JWT secret.
Closing the Laptop
The End-of-Day Wrap is a ritual. It takes 3 minutes. It's a commit message for your workday. Once you send it, you are culturally permitted to be offline.
The Project Representative
StandIn ingests your wrap, your linked tickets, and your PR status. It becomes a read-only API for your context while you sleep.
Reference: PR #482 (Open)
Built for Engineering Culture
No Monitoring
We do not count keystrokes, commits per hour, or active time. We are infrastructure, not spyware.
Silence is Respected
If you don't wrap, StandIn stays silent. It doesn't nag or hallucinate. It respects the void.
No Speculation
StandIn refuses to answer "What do you think Sarah meant?". It only reports declared state.
System of Record
We treat Jira/Linear/GitHub as truth. We don't try to reinvent your project management.
When NOT to use StandIn
This is not for teams that require real-time, synchronous availability (e.g. L1 Incident Response rooms).
StandIn adds a buffer. It is designed for asynchronous depth, not instant chat speed.