← All architectures
ARCHITECTURE / BOUNDARIES AND AUTHORITY
Records become evidence. Decisions stay accountable.
The operational audit separates deterministic preparation, bounded semantic review and validated reporting. Recovery preserves evidence instead of silently accepting a missing output.
ORDERED FLOW / 8 STAGES
01
Snapshots
02
Period paths
03
Facts + batches
04
Semantic review
05
Consolidation
06
SQL transaction
07
History + exports
08
Analyst decision
INPUT / HISTORY
Daily changes and occasional full-backlog snapshots retain repeated incident records as treatment history.
SEMANTIC CONTRACT
Deterministic facts and calculations precede bounded review. The supplied review contract uses 34 columns and an indexed 12-file knowledge base.
What crosses each boundary.
01 / ServiceNow snapshots
Daily changes and occasional full backlog capture the operational record. Repeated incidents preserve treatment history.
02 / Path_Builder
Organizes period-based paths for inputs, outputs, quarantine and logs.
03 / build_agent
Extracts deterministic facts with regex; prepares calculations, bounded batches, tailored prompts and audit anchors.
04 / RPA + Compliance Agent
The UI executor checks coverage, retries, quarantines and resumes from anchors. Semantic review uses the indexed KB and the 34-column output contract.
05 / Consolidator
Checks successful days and anchors, then produces validated input, gaps, coaching and KPI views.
06 / Transactional load
Validates the column contract, sanitizes extra fields and normalizes values before an idempotent, all-or-nothing SQL load.
07 / SQL + export_backlog
RAW retains repeated records and source metadata. STG/MART derive active and historical views for reporting and sanitized exports.
08 / Intelligent Backlog
Consults incident dossiers, active backlog, history and daily Teams evidence. Sources and search limits stay visible; the analyst owns the decision.
VALIDATION / RECOVERY
Coverage checks, retries, quarantine and audit anchors distinguish accepted outputs from gaps and support controlled resumption.
TRANSACTIONAL BOUNDARY
Normalize and validate fields before an idempotent, all-or-nothing SQL load. RAW history remains separate from derived active and historical views.
HUMAN AUTHORITY
Intelligent Backlog assembles dossiers, backlog, history and daily Teams evidence. The analyst verifies the sources and makes the decision.
PUBLIC EVIDENCE
The declared reporting scope is 68 KPIs across 12 domains. This logical view exposes no incident records or client infrastructure and establishes no live connection.
Read the full case ↗
All seven architectures ↗
About the work and career ↗
VALTER LOURENÇO JUNIOR / NCMA SYSTEMS
← All architectures
ARCHITECTURE / BOUNDARIES AND AUTHORITY
Records become evidence. Decisions stay accountable.
The operational audit separates deterministic preparation, bounded semantic review and validated reporting. Recovery preserves evidence instead of silently accepting a missing output.
ORDERED FLOW / 8 STAGES
01
Snapshots
02
Period paths
03
Facts + batches
04
Semantic review
05
Consolidation
06
SQL transaction
07
History + exports
08
Analyst decision
INPUT / HISTORY
Daily changes and occasional full-backlog snapshots retain repeated incident records as treatment history.
SEMANTIC CONTRACT
Deterministic facts and calculations precede bounded review. The supplied review contract uses 34 columns and an indexed 12-file knowledge base.
What crosses each boundary.
01 / ServiceNow snapshots
Daily changes and occasional full backlog capture the operational record. Repeated incidents preserve treatment history.
02 / Path_Builder
Organizes period-based paths for inputs, outputs, quarantine and logs.
03 / build_agent
Extracts deterministic facts with regex; prepares calculations, bounded batches, tailored prompts and audit anchors.
04 / RPA + Compliance Agent
The UI executor checks coverage, retries, quarantines and resumes from anchors. Semantic review uses the indexed KB and the 34-column output contract.
05 / Consolidator
Checks successful days and anchors, then produces validated input, gaps, coaching and KPI views.
06 / Transactional load
Validates the column contract, sanitizes extra fields and normalizes values before an idempotent, all-or-nothing SQL load.
07 / SQL + export_backlog
RAW retains repeated records and source metadata. STG/MART derive active and historical views for reporting and sanitized exports.
08 / Intelligent Backlog
Consults incident dossiers, active backlog, history and daily Teams evidence. Sources and search limits stay visible; the analyst owns the decision.
VALIDATION / RECOVERY
Coverage checks, retries, quarantine and audit anchors distinguish accepted outputs from gaps and support controlled resumption.
TRANSACTIONAL BOUNDARY
Normalize and validate fields before an idempotent, all-or-nothing SQL load. RAW history remains separate from derived active and historical views.
HUMAN AUTHORITY
Intelligent Backlog assembles dossiers, backlog, history and daily Teams evidence. The analyst verifies the sources and makes the decision.
PUBLIC EVIDENCE
The declared reporting scope is 68 KPIs across 12 domains. This logical view exposes no incident records or client infrastructure and establishes no live connection.
Read the full case ↗
All seven architectures ↗
About the work and career ↗
VALTER LOURENÇO JUNIOR / NCMA SYSTEMS