Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ created_at: 2026-04-30T12:00:00Z
- `task-timers.json` sidecar: JSON array of optional `FocusTimer` values. Array index matches the parsed task index; deleting a Task removes the matching timer entry. Expiry writes update the indexed timer to `status: Expired` atomically. Corrupted or missing task timer sidecars degrade to no task timers.
- User hand-edits anywhere; file watcher reflects changes.
- Atomic write via tmpfile + rename, serialized by an exclusive lock file per target.
- First launch seeds one example Focus. A marker file stops it from coming back after the user clears every Focus.
- Startup loads saved Focuses, Tasks, Timers, and Settings without creating example work. With no saved work, the ranch starts empty. Existing example Focuses and legacy `.example-focus-seeded` files remain untouched; Timers keep their saved start/duration and follow normal expiry, including time elapsed while the app was closed.

## Timers

Expand Down
35 changes: 35 additions & 0 deletions issues/063-resume-saved-work.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# 063 — Resume saved work without startup examples

## Owning specification

`specs/003-ranch-today/spec.md`: FR-001, FR-019, US1/AC4–AC5; `plan.md#startup-correction-slice`; tasks T030–T035. These feature artifacts remain Draft. The owner explicitly selected no seeding and resumption from saved work on 2026-10-18, then requested implementation. This narrow correction follows that direction without promoting other Draft features.

## What to build

Remove the automatic example writer: delete `src-tauri/src/app/seed.rs` and its module declaration/call in `src-tauri/src/app/mod.rs`. Update `docs/architecture.md`. Reuse existing work/Settings loading and Timer expiry; preserve old examples and marker files. No replacement service, flag, onboarding, schema/data migration, click-through fix, or Agent change.

## Completion promise

Ranch starts from the person's saved work and Settings, creates no example Focus or Task, and starts empty when no saved work exists, without resetting or deleting existing work or restarting Timers.

## Acceptance criteria

- [x] Automatic example creation and its marker writer are removed from startup; no replacement work writer is introduced.
- [ ] Saved Focuses/Tasks/Settings and old examples remain intact; legacy markers stay untouched and do not affect startup behavior.
- [ ] Empty roots with/without a legacy marker remain empty across launch/restart (V0).
- [ ] Future/Expired/due-while-closed Focus/Task Timers retain start/duration and follow normal expiry; canonical work is unchanged (V0).
- [x] Architecture documentation matches the correction.
- [x] Fresh `rtk task check` and `rtk task check:windows` pass on synchronized corrected source.
- [ ] Independent review, current-head green CI, and merge are recorded; native acceptance remains open until actual V0 proof exists.

## Constitution compliance

I: remove an unauthorized writer; preserve user-owned data and timer-only expiry. II–IV: retain independent domains, existing typed boundaries, and opt-in integration behavior. V: one narrow correction, current-source gates and actual native evidence before acceptance claims. VI: distinguish owner direction, implementation, historical evidence, and Draft artifacts. No exception or new architecture decision is proposed.

## Blocked by

No code prerequisite. Native startup proof is explicitly deferred until the owner resumes testing. This issue must not be moved to `issues/done/` or called fully accepted without that proof. The separate open-card click-through gap does not block this startup-only correction.

## User stories addressed

US1/AC4–AC5. Full US1 and all six baseline success criteria retain their actual separate status.
81 changes: 81 additions & 0 deletions specs/003-ranch-today/checklists/baseline.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
# Baseline Requirements Checklist: Ranch Today

**Purpose**: Review the completeness, clarity, consistency, and measurability of 003's requirements, emphasizing local work/Timer rules and acceptance boundaries.
**Created**: 2026-10-18
**Feature**: [Ranch Today specification](../spec.md)
**Depth**: Standard — 30 requirements-quality questions.
**Audience / Timing**: Reviewer; requirements review before the next specification revision or acceptance discussion. Suitable for PR review, not a runtime test procedure.
**Input**: `$speckit-checklist` with no additional focus supplied; standard scope selected from the current spec, plan, and tasks.

**Note**: This custom checklist is generated by `$speckit-checklist` from feature context and requirements.
**Review Ownership**: This is a reviewer-owned requirements-quality artifact. Mark an item `[x]` only when the reviewer determines its requirements-quality criterion is satisfied.
**Marker Semantics**: `[x]` means reviewed and satisfied for requirements quality. It does not mean implementation work is complete or product acceptance has passed.

**Constitution Alignment**: Questions cover local-state safety (I), independent domains (II), boundary ownership (III), explicit integration authority (IV), observable acceptance (V), and source/status authority (VI). Creating this checklist grants no compliance result, exception, or Draft-status promotion.

## Requirement Completeness

- [ ] CHK001 Are canonical work records, Timer ownership, and permitted work writers explicitly defined? [Completeness, Spec §FR-001, §FR-019]
- [ ] CHK002 Are requirements for Focus duplication and Task editing/undo explicit about which work and Timer state is retained? [Completeness, Gap, Spec §User Story 2, §FR-002–FR-003]
- [ ] CHK003 Are saved-duration validity, uniqueness, sharing, persistence, and removal rules stated consistently across the requirements and data model? [Completeness, Spec §FR-003; Data Model §User-owned work]
- [ ] CHK004 Is what counts toward each Limit explicitly defined, including completed Tasks and expired Focuses? [Completeness, Gap, Spec §FR-007; Data Model §User-owned work]

## Requirement Clarity

- [ ] CHK005 Is “a glance is enough” defined by an observable identification outcome and the conditions under which it applies? [Clarity, Ambiguity, Spec §User Story 1, §SC-001]
- [ ] CHK006 Is “within about a second” bounded by a stated tolerance and clear start/end events? [Clarity, Ambiguity, Spec §User Story 4, §SC-003]
- [ ] CHK007 Are Running, Expired, Clear, restart, and Revive distinguished without conflating Focus and Task Timer effects? [Clarity, Spec §FR-002–FR-003, §User Story 2; Data Model §State transitions]

## Requirement Consistency

- [ ] CHK008 Are Focus and Agent Session ownership, editability, Timer eligibility, and Limit contribution consistent across stories and requirements? [Consistency, Spec §FR-005, §FR-007, §FR-010]
- [ ] CHK009 Are notification permission, source-specific enablement, and per-crossing frequency requirements consistent with the allowed-attention rule? [Consistency, Spec §Edge Cases, §FR-017, §SC-004, §User Story 2/AC5]
- [ ] CHK010 Are app-authored Settings changes and external Settings edits assigned consistent immediate-versus-next-launch semantics? [Consistency, Spec §Edge Cases, §FR-008]
- [ ] CHK011 Are product-runtime network restrictions reconciled with the explicitly permitted external effects of integration installation? [Consistency, Conflict, Spec §FR-011–FR-012, §SC-006; Constitution I, IV]

## Acceptance Criteria Quality

- [ ] CHK012 Does each success criterion identify an observable outcome and sufficient conditions for a reviewer to judge it objectively? [Measurability, Spec §SC-001–SC-006]
- [ ] CHK013 Are success criteria traceable to requirements and acceptance scenarios, including Agent exclusion from Limits? [Traceability, Spec §FR-007, §SC-004–SC-005, §User Stories 3 and 5]
- [ ] CHK014 Are package-build acceptance and native product acceptance defined as distinct claims with distinct evidence requirements? [Measurability, Spec §FR-016, §SC-001–SC-006; Plan §Validation Slices; Tasks §Phase 9]
- [ ] CHK015 Are evidence-assessment completion, demonstrated acceptance, and owner-deferred acceptance clearly distinguished in the documented completion rules? [Clarity, Spec §Constitution Compliance Check; Tasks §Organization, §Phase 9/Completion rule, §Owner execution direction; Constitution V]

## Scenario Coverage

- [ ] CHK016 Are both app-authored work and external Markdown edits covered without changing canonical ownership or the permitted writer boundary? [Coverage, Spec §FR-001, §FR-019, §User Stories 2 and 4]
- [ ] CHK017 Are restart, time spent while Ranch is absent, and already-due Timer scenarios covered by requirements or explicitly left unresolved? [Coverage, Gap, Spec §FR-003, §User Story 2]
- [ ] CHK018 Are missing integration prerequisites, installation failure, and interrupted repair covered by requirements or explicitly excluded? [Coverage, Gap, Spec §FR-011; Constitution IV]
- [ ] CHK019 Are sessions already active before observation starts distinguished from sessions subsequently observed through Hook Firings? [Coverage, Spec §User Story 5/Current limitation, §SC-005]

## Edge Case Coverage

- [ ] CHK020 Are malformed canonical work records distinguished from missing or corrupt optional Timer state in the stated failure requirements? [Edge Cases, Gap, Spec §FR-001, §Edge Cases]
- [ ] CHK021 Are blank work text and invalid custom durations assigned explicit requirements, including nonpositive, duplicate, and built-in-equivalent durations? [Edge Cases, Gap, Spec §FR-001, §FR-003; Data Model §User-owned work]
- [ ] CHK022 Are empty-ranch state, deletion cancellation, and the persistence of the first-launch seed decision fully specified? [Edge Cases, Spec §Edge Cases, §User Story 3/AC3]

## Non-Functional Requirements

- [ ] CHK023 Are failure reporting, atomic persistence, and preservation of existing work specified for interrupted or rejected work changes? [Completeness, Gap, Spec §FR-001; Constitution I]
- [ ] CHK024 Are keyboard and assistive-access requirements for work cards, Timer controls, and Settings specified or intentionally excluded? [Coverage, Gap, Spec §User Stories 2 and 3, §FR-005, §FR-008]
- [ ] CHK025 Are privacy requirements for integration configuration and diagnostic records explicit about credential and transcript boundaries? [Completeness, Gap, Spec §FR-011–FR-012; Constitution I, IV]

## Dependencies & Assumptions

- [ ] CHK026 Are supported-platform and integration prerequisites explicit, including the boundary of unsupported Windows hook delivery? [Dependencies, Spec §FR-016, §Edge Cases; Plan §Technical Context]
- [ ] CHK027 Are configuration health and observed hook delivery defined separately, without assuming one proves the other? [Clarity, Assumption, Spec §FR-011, §User Story 5/AC4; Constitution IV]
- [ ] CHK028 Are known limitations, Accepted ADR direction, and Draft follow-on proposals classified so that observations do not become preservation requirements or implicit new scope? [Traceability, Spec §Clarifications, §Constitution Compliance Check, §FR-013–FR-015; Plan §Summary; Constitution VI]

## Ambiguities & Conflicts

- [ ] CHK029 Are empty-overlay interaction requirements reconciled with the interactive area required by an open Focus card? [Conflict, Spec §FR-004–FR-005, §User Story 2]
- [ ] CHK030 Is automatic first-launch example creation explicitly reconciled with the restriction on who may author work? [Conflict, Spec §Edge Cases, §FR-001, §FR-019; Constitution I]

## Notes

- Review the requirements as written; these questions are not instructions to exercise the app or certify its behavior.
- Leave items unchecked until the reviewer explicitly evaluates them. `[Gap]`, `[Ambiguity]`, `[Conflict]`, and `[Assumption]` identify review targets, not confirmed findings or authorized scope additions.
- `$speckit-implement` reads checklist checkbox state as a gate and must not modify these markers.
- `checklists/requirements.md` has a separate built-in lifecycle maintained by `$speckit-specify` and `$speckit-clarify`; this custom `baseline.md` does not use that exception.
- The owner's deferred native testing remains separate in [tasks T023–T028](../tasks.md#phase-9-convergence); successful package builds do not settle those acceptance claims.
- Add reviewer findings beside the relevant CHK ID. Proposed requirements changes need their own decision; the checklist does not amend the spec, plan, tasks, or Accepted ADRs.
- References: [spec](../spec.md), [plan](../plan.md), [tasks](../tasks.md), [data model](../data-model.md), [constitution](../../../.specify/memory/constitution.md). Section references describe written requirements, not implementation results.
Loading
Loading