Skip to content

docs(c4): model time entry store as internal datastore - #17

Draft
lhohan wants to merge 1 commit into
mainfrom
codex/investigate-modeling-issue-with-c4
Draft

lhohan wants to merge 1 commit into
mainfrom
codex/investigate-modeling-issue-with-c4

Conversation

@lhohan

@lhohan lhohan commented Mar 29, 2026

Copy link
Copy Markdown
Owner

Motivation

  • The previous C4 DSL represented the markdown time-entry files as an external system, but the application reads/writes a filesystem path provided to the running Time Tracker (via --input or web default resolution), so the storage is better modeled as an internal, file-backed datastore inside the system.

Description

  • Added a Time Entry Store container inside the Time Tracker software system in docs/c4/time-tracker.dsl to represent file-backed markdown storage (Markdown files on filesystem).
  • Rewired relationships so the CLI and Web containers and the input-processing components read from timeTracker.timeEntryStore instead of an external system, and added a User -> timeTracker.timeEntryStore relationship to indicate user-maintained files.
  • Removed the unused External Data Store style element from the DSL so styling matches the new internal datastore model.
  • Kept all changes limited to the C4 model file docs/c4/time-tracker.dsl and did not change runtime code.

Testing

  • Ran cargo check and it completed successfully with no errors.
  • Attempted to run just architecture-docs-validate but it could not run in this environment because just is not installed.

Codex Task

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant