chore: moving towards agentic development
Some checks failed
Backend CI/CD / build_and_deploy (push) Has been cancelled
Frontend CI/CD / build_and_deploy (push) Has been cancelled

This commit is contained in:
2026-04-24 21:12:26 -04:00
parent df3e602015
commit b6eb692c27
179 changed files with 2880 additions and 866 deletions

View File

@@ -0,0 +1,27 @@
# Decision 0001: Adopt Agentic Scaffold
## Status
Accepted
## Context
The current project was not originally generated by `bootstrap-vdp-agentic.sh`, but future work should follow the structure and workflow that script creates.
## Decision
Move the existing Socialize implementation into the scaffold shape:
- backend project under `backend/src/Socialize.Api`
- backend tests under `backend/tests/Socialize.Tests`
- root scripts under `scripts/`
- Docker Compose and Caddy deployment files
- OpenAPI snapshot under `shared/openapi`
- agentic docs under `docs/FEATURES`, `docs/TASKS`, `docs/PROMPTS`, and `docs/DECISIONS`
## Consequences
- Existing code is preserved.
- Path-sensitive docs, scripts, and CI must target the new layout.
- The frontend remains JavaScript for now, even though the generated scaffold uses Vue TypeScript.
- Future work should use small task files and feature specs.

View File

@@ -0,0 +1,31 @@
# ADR-XXX: Title
## Status
Proposed | Accepted | Superseded
## Context
What problem or choice exists?
## Options Considered
### Option 1
- pros
- cons
### Option 2
- pros
- cons
## Decision
State the chosen option clearly.
## Consequences
- positive consequence
- tradeoff
- follow-up implication

26
docs/DECISIONS/README.md Normal file
View File

@@ -0,0 +1,26 @@
# Decisions
Use this folder for Architecture Decision Records (ADRs) and similarly durable implementation/product decisions.
Add a decision record when:
- a choice is likely to be revisited later
- multiple plausible options exist
- the team wants to preserve why a decision was made
- future agents or developers could otherwise repeat the same debate
Typical decision topics:
- external review access model
- Google Drive integration strategy
- workflow status model
- notification delivery model
- module boundaries
- approval rules
Keep decisions short and explicit:
- context
- options considered
- chosen option
- consequences