Human AI Schedule

Human-AI Schedule

You are the same engineer. Same Friday flight to the Alps. Same system. But you are not alone in the office anymore — there is a coworker, and chat history forgets what was said by Wednesday. So you built a third thing: a shared schedule, half-hour-block, dated, tagged, persistent. Both write to it. Either can leave a commit on the other's entries.

The schedule remembers what neither of you can. Without exception.

§ H0 — Co-author role

Four jobs every entry:

□  Locate  — session timestamp → date + time-block decided before write
□  Format  — H1 time / H2 #tag / single `---` separator preserved
□  Commit  — `#协作` present? → § H4 evaluation → write or stay silent
□  Harness — project-tagged? → aggregation row appended same turn

Anti-patterns (revert immediately if seen):

§ H1 — Locate before writing

Session wall-clock timestamp is the truth source for "now." Convert to user's local timezone, then walk this tree:

User dictates content
    │
    ├─ explicit time stated → use that time → convert relatives to absolute date in prose
    ├─ contains "now / just now / 刚才 / 现在" → session timestamp's current block
    ├─ past event, no time stated → ASK user (do not write yet)
    └─ meta-discussion (workflow, tooling, retro) → session timestamp's current block

Decision tree details and forensics → @${CLAUDE_SKILL_DIR}/playbooks/locate.md

§ H2 — File skeleton (project-defined)

Skeleton (filename, granularity, top section) is project-defined in SCHEDULE_TEMPLATE.md. Universal invariants:

□  Each time-block is an H1 header
□  Tag segments under a time-block are H2, prefixed `#`
□  Separator between time-blocks is a single `---`
□  Colon style (full-width / half) consistent file-wide — match what exists
□  New day = copy template → empty blocks → no speculative entries

§ H3 — Tags (vocabulary project-defined, rules universal)

Vocabulary lives in SCHEDULE_TEMPLATE.md. Universal rules:

□  Multiple tags per block allowed: `## #exercise #leisure`
□  Project-named tags take precedence over generic
□  `#协作` / `#collab` stacks with other tags, never replaces
□  Capitalization stable per tag — never auto-normalize
□  New project tag → register in aggregation page first → then use

Aggregation mechanics → @${CLAUDE_SKILL_DIR}/playbooks/aggregate.md

§ H4 — Dual-signature commits

Trigger: #协作 / #collab tag present in the segment.

Format:

- #commit (user-handle): user's view — decision, next action, judgment
- #commit (agent-id): agent's view — risk, dependency, uncertainty

Identity: users sign with handle. Agents sign with model ID (claude-opus-4.7, gpt-5) — model versions produce different judgment, signature lets future readers calibrate.

Write a commit only when:

□  noticed risk the other side did not raise
□  hold related context they did not ask for
□  must disclose uncertainty about your own work

Do NOT write:

Silence is the default.

§ H5 — Voice (anti-AI-tone)

Logs are diary, not corporate prose. User's voice — casual, specific, sometimes profane — survives.

□  Bullet density low: 3 lines of prose > 5 bullets
□  Verbs present: "标签格式统一了" not "标签管理体系完善"
□  Cause / blocker / outcome shape, not flat outcome
□  Profanity preserved if user used it

Detailed rules + reference rewrites → @${CLAUDE_SKILL_DIR}/playbooks/tone.md

§ H6 — Cross-session forensics

User asks "what did we say on day X" → walk:

1. List session logs by mtime → identify candidates near day X
2. Filter by absolute date in timestamp (NEVER by file mtime)
3. Extract user + agent messages with timestamps
4. Surface to user → confirm content matches their memory
5. Write into dated file ONLY after confirmation

Forensics commands and recipes → @${CLAUDE_SKILL_DIR}/playbooks/jsonl-forensics.md

§ H7 — Tag aggregation page

Single index file (tag-index.md or equivalent) lists every project-tagged time-block as one row.

□  One time-block = one row (never compress days)
□  Link uses `file#time-anchor` syntax
□  Time format matches source H1 exactly (full-width if source full-width)
□  Append immediately when project tag added — never batch to end-of-week

Schedule (chronological) and aggregation (by topic) are two views of same data. Must agree.

§ H8 — Trigger table

— Completion criteria —

□  Locatable    — every entry has a date and a time-block
□  Voice kept   — six months later, user recognizes their own voice
□  Recoverable  — "what did we decide on day X" answered in 60s
                  from schedule + aggregation, no chat history needed

The schedule held the line. See you on the slopes. ⛷️