Files
dtf-system/docs
Cauê Faleiros 8b42e684ca
All checks were successful
Build and deploy / Validate source (push) Successful in 10s
Build and deploy / Integration suite on a real stack (push) Successful in 2m46s
Build and deploy / Secret scan and release gate (push) Successful in 6s
Build and deploy / Publish images (push) Successful in 1m46s
docs: record the Tiny account and product findings
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 13:40:28 -03:00
..

Documents

File What it is
reuniao-2026-09-09-anotacoes.pdf Meeting notes that set the business direction: the bottleneck, the 24h goal, the automation and payment decisions. Still the record of what was asked for.
roadmap-cliente.pdf The client-facing plan, as last sent. Generated by tools/generate_dtf_report.py; regenerate rather than edit.
historico/ The original specification and prototype documents. Background only — they describe a model this system does not implement.

Current engineering documents live at the repository root: CONTEXT.md for how the system works, ROADMAP.md for what is outstanding, LOCAL_SETUP.md to run it, PORTAINER.md to deploy it, SECURITY_REPORT.md and PRODUCTION_INPUTS.md for the security position and the decisions still owed by the client.

Weekly client reports are deliverables, not repository content. They are produced for a specific week and are deliberately not versioned here.