/as:timetracker

Before acting, read the host contract, this component's declaration (skill:timetracker), and applicable workspace semantics. Load only the required modes from the shared catalog.

Use the host adapter and native context procedure. The harness performs the semantic operations below using its available native tools; ordinary task-specific code is allowed. No Arch Studio runtime, installer, bridge, supplied script or source checkout is required. Direct skill invocation is valid. Existing exact authorization persists; ask only for material missing facts or unavailable access.

Own project TIME.csv. Resolve one valid project through context.resolve; folders, Git roots and current directory alone never establish a project. A standalone valid project needs no studio.

Before changing records

Before persistent changes, follow the native mutation sequence: Inspect → Prepare → Verify preparation → Apply → Verify result → Complete. Inspect pending work first. Finish and verify preparation before the first canonical write: separately reread every saved original and prepared file, check its complete actual bytes, establish durable saving, and inspect actual permissions, ownership and ACLs. Merely writing recovery files does not finish verification. Apply only that verified set. Mark complete only after fresh readback validates the entire affected result and its relationships. Read-only requests and inline drafts need no publication sequence.

Time append/correction affects the complete TIME.csv only. Selected project/document/source records are read guards; their existence does not authorize edits or inferred hours. A correction preserves the original entry and adds one new confirmed entry under the ledger semantics.

Resolve the requested period; ask if absent. Perform time.list as native reads, then read the selected project’s DOCUMENTS.csv for relevant dated plans/decisions/events and inspect PROJECT.md, TASKS.csv and selected source artifacts. Explicit semantic work/event dates take priority; Git or modification times may suggest evidence but never duration. Report sources inspected and unavailable channels; quiet records do not prove no work or a complete timesheet.

Prepare descriptions with blank hours, stable source document IDs/items and confidence. Group evidence for the same activity; don't inflate it by file counts. Flag evidence already logged. Every finite positive duration comes from the user; meeting lengths, timestamps, commits and task status never supply hours. Unknown source/work dates remain unresolved.