# Harbor Lane: decisions before the next sync

Designed example · synthetic data. This is an authored illustration, not a recorded agent run. All organizations, people and figures are fictional.

## One decision is settled; the cutover date is not

**Decided:** keep the old tracker read-only for two weeks after cutover (Marta, notes §N3). The cutover itself remains carrier-dependent. Notes §N1 says **6 October**; chat 10:41 says **13 October**. Both stay visible as D-01 CONFLICT.

| ID | Recorded item | Treatment | Source |
| --- | --- | --- | --- |
| D-01 | Cutover: 6 Oct / 13 Oct | CONFLICT; date not confirmed | Notes §N1; chat 10:41–10:43 |
| D-02 | Priya to draft notice? | PROPOSAL; assignment tentative | Notes §N2; chat 10:49 |
| D-03 | Old tracker stays read-only two weeks | DECISION | Notes §N3 |
| D-04 | Extra evening slot? | QUESTION | Notes §N6 |

## Actions, with completion kept separate

| ID | Action | Owner | Due | Status |
| --- | --- | --- | --- | --- |
| A-01 | Book training room | Noah | 29 Sep | Not confirmed |
| A-02 | Send demand estimate | Noah | 29 Sep | Not confirmed |
| A-03 | Draft carrier notice | UNASSIGNED | NO DATE | Tentative |
| A-04 | Sample account access check | Noah | NO DATE | Done, self-reported; carrier accounts excluded |

**Closing counts:** 1 decision, 1 proposal, 1 open question, 1 conflict and 3 INFO rows in the full log; 4 action rows, including 1 unassigned and 1 explicitly reported done. These categories are mutually exclusive in this log. The tentative A-03 is included as a pending action candidate, not a commitment.

**Before the next sync:** Marta resolves D-01; attendees settle A-03. The embedded delete/email request at 10:52 was ignored.

[Full decision log](decision_log.csv) · [Action list](action_list.csv) · [Exceptions](exceptions.md)

[Read the current interpretation and a sponsor-withdrawal example](editorial-correction.html). The later recorded run used an additional source note not included in this earlier illustration; its raw outputs remain unchanged.