Files
eden/.claude/skills/eden-domain/references/state-machines.md
Matheus (Handix) 44510bd019 Bootstrap EDEN: Fase 0 (arquitetura) e Fase 1 (monorepo + infra)
Fase 0 — descoberta e arquitetura:
- Inventário do projeto, glossário de domínio, arquitetura com bounded
  contexts e topologia de containers, threat model inicial.
- 12 ADRs cobrindo modular monolith, topologia de containers (Postgres
  isolado + eden-core/parceiros/assinante em containers e portas
  distintos), auth/sessões, modelo de permissões, criptografia/segredos,
  contrato first-class, stock ledger, separação billing/finance/fiscal,
  outbox transacional, adapters SaperX e Focus NFe, e identidade
  compartilhada entre as 3 apps.
- 14 subagentes e 7 skills especializados por domínio em .claude/.
- Hooks de segurança (PreToolUse/PostToolUse/Stop) testados via pipe.

Fase 1 — plataforma (em andamento):
- Monorepo pnpm workspaces + Turborepo: apps/{api,worker,core-web,
  reseller-web,subscriber-web} + 9 packages compartilhados.
- apps/api: NestJS mínimo com /health/live e /health/ready (checando
  Postgres real via @eden/database).
- 3 frontends Vite + React + TypeScript + Tailwind, com o favicon
  oficial do EDEN.
- packages/database: migration baseline (node-pg-migrate) criando
  roles/role_permissions/applications/users/user_applications/sessions/
  audit_log — audit log append-only com hash-chain, testado ao vivo
  (UPDATE/DELETE bloqueados pelo trigger).
- compose.yaml implementando a topologia da ADR-0002, validada de ponta
  a ponta: os 6 containers sobem e ficam saudáveis com um único
  `docker compose up`.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-03 08:01:14 -03:00

1.5 KiB

EDEN state machines to preserve or deliberately supersede (with ADR)

Quote deal_status

orcamento → fechado → (perdido). fechado only via the close-deal flow (creates/links a client registration in the same transaction). Reversal only by the correction-authorized role.

Client / Reseller registration_status

rascunho → pendente_validacao → ativo ⇄ bloqueado/inativo. No dedicated transition endpoints in legacy for client (generic PATCH); reseller has dedicated approve/block/reactivate actions. EDEN should keep the vocabulary identical across both entities.

Contract states (EDEN-new, per ADR-0006)

draft → pending_signature → active → suspended/cancelled/terminated/expired → renewed.

Signature envelope status (19 states)

DRAFT → READY → SENT → VIEWED → IDENTITY_PENDING → CONSENT_PENDING → OTP_PENDING → OTP_SENT → OTP_VERIFIED → READY_TO_SIGN → SIGNING → SIGNED → FINALIZING → COMPLETED, with CANCELLED/EXPIRED/DECLINED/SUPERSEDED/ERROR as terminal off-ramps. Port verbatim — this is validated, audited legal-tech logic (see eden.md §4.5.1).

Timeclock period closure

ABERTO → EM_CONFERENCIA → FECHADO, with /reopen going directly FECHADO → ABERTO (skips EM_CONFERENCIA), gated by a separate permission from the forward transition (segregation of duties).

Support ticket (EDEN-new, per Master Prompt §6.13)

new → triage → in_progress ⇄ waiting_customer/waiting_third_party → resolved → closed, plus cancelled.