Skip to content

feat: application status transition flow - #13

Merged
Treggats merged 4 commits into
feature/data-modelfrom
feature/status-transitions
Sep 3, 2026
Merged

feat: application status transition flow#13
Treggats merged 4 commits into
feature/data-modelfrom
feature/status-transitions

Conversation

@Treggats

@Treggats Treggats commented Sep 3, 2026

Copy link
Copy Markdown
Owner

Status transition behaviour on top of the data model.

  • ApplicationStatus::canTransitionTo() / statusChange(): forward-only,
    terminal-final state machine
  • applied can go straight to rejected/withdrawn without an interview;
    offer stays reachable only from interviewing
  • Reapplying after a terminal status creates a new Application record,
    never a status revert
  • v1 spec restructured (TOC, status flow table, draft screens checklist,
    validation placeholders) and decisions recorded in .ai/decisions.md

Stacked on #12 (data model).

- v1.md: add TOC, explicit status transition table, draft screens
  checklist, and a validation placeholder section
- decisions.md: record that status transitions are forward-only/
  terminal-final (reapplying creates a new Application record),
  transition legality lives on ApplicationStatus::canTransitionTo(),
  and Companies get a standalone index screen
Record the decision and update the v1 status flow table: a rejection or
withdrawal doesn't have to pass through interviewing, matching what
ApplicationStatus::canTransitionTo() now implements. offer stays reachable
only from interviewing.
Allow for the application status to progress
@Treggats
Treggats force-pushed the feature/status-transitions branch from 289103c to c753afc Compare September 3, 2026 08:34
@Treggats
Treggats merged commit 9d30d94 into main Sep 3, 2026
1 check passed
@Treggats
Treggats deleted the feature/status-transitions branch September 3, 2026 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant