Advisory Time Boundary — Synchronous Weekend Block, Asynchronous Off-Hours
Advisory availability is bounded: synchronous interaction in a defined weekend block, asynchronous replies after normal working hours, no weekday real-time availability. One midweek exception per occurrence; recurring urgency is deferred to the next scheduled window. Implicit availability is the primary failure mode of informal advisory arrangements — without explicit terms, urgency creates pull, pull creates obligation, and obligation converts advisory into shadow employment. Language to avoid: 'always available for a quick call,' 'just ping me,' 'think of me as part of the team.' Correct framing: available in the weekly window and asynchronously off-hours; exceptions are opt-in, not default.
Capture
The advisory engagement has explicit time boundaries. These are stated here to prevent implicit availability creep from converting an advisory arrangement into shadow employment.
Default protocol:
- Synchronous interaction occurs in a defined weekend time block.
- Asynchronous replies (email, written review) occur after normal weekday working hours.
- No weekday real-time availability is implied or expected.
- No midweek standing availability exists.
Exception policy:
- One off-cycle exception may be accommodated if the partner raises a genuinely urgent issue midweek.
- After the first occurrence, recurring midweek urgency is deferred to the next scheduled window.
- The operator does not reschedule other commitments to accommodate venture urgency.
- "Urgent" is defined by the partner's characterization, but the operator reserves the right to defer if the primary employment commitment would be affected.
What "availability" does and does not mean:
- Available: accessible in the scheduled window; responsive to asynchronous requests within a reasonable post-hours window.
- Not available: responsive to requests during core work hours; accessible for real-time problem-solving on demand; reachable for same-day turnaround outside the scheduled window.
Why
Implicit availability is the primary failure mode of informal advisory arrangements. Without explicit terms, the partner will naturally treat advisory availability as proportional to their need. Urgency creates pull. Pull creates obligation. Obligation converts an advisory relationship into informal employment — with all the time cost and none of the formal protections. The boundary exists to prevent that conversion before it happens.
The full-time role is the primary constraint. Not a secondary consideration, not a soft preference — the primary constraint. Any advisory structure that introduces unpredictable weekday demands directly competes with the primary employment obligation. The time boundary is the protection mechanism.
Explicit terms are better than assumed terms. Assumed terms are renegotiated implicitly, under pressure, in the moment. Explicit terms are renegotiated deliberately, when both parties are calm. Stating the boundary in the founding record ensures it is treated as established, not as the operator being difficult.
Why-Not
Why not leave availability flexible and handle it case by case? Case-by-case availability defaults to "yes" under social pressure. The operator's natural inclination to be helpful will, without a stated boundary, produce a pattern of accommodation that erodes the boundary over time. Explicit terms move the decision upstream, where it can be made without pressure.
Why not define availability in a formal contract? A formal engagement contract adds legal overhead and creates a principal-agent structure with defined deliverables, which is inconsistent with the advisory-only posture in C7-010. The boundary defined here is an operating principle, not a service agreement.
Why not allow the weekend block to expand as the relationship develops? Expansion is available — it requires explicit renegotiation, not assumption. The default is contained. Expansion is opt-in.
Risks and Language to Avoid
The following phrases create implicit availability and should not appear in any oral or written framing of this arrangement:
- "Always available for a quick call" — there is no always-available posture.
- "Just ping me when you need something" — implies on-demand access.
- "I'll be around on weekdays for anything important" — eliminates the boundary.
- "We can figure out the timing as we go" — defers the boundary to conditions where it will be harder to enforce.
- "Think of me as part of the team" — team framing implies operational standing.
The correct framing: "I'm available for strategic input in the weekly window and asynchronously after hours. For things that can't wait, send a note and I'll decide if the exception applies."
Commit
Decision: Advisory availability is bounded to a synchronous weekend block and asynchronous off-hours responses. No weekday real-time availability. One midweek exception accommodated per occurrence; recurring midweek urgency deferred to the next window. The full-time role is the primary obligation; the advisory engagement does not create any competing claim on that time.
Confidence: High.
Timestamp
2026-04-26