Connector Forge

Security feeds can repeat records, arrive out of order, and disagree. A useful inventory needs consistent merge behavior and a way to explain where each field came from.

I built the Python/SQLite ingestion core, service integration, evidence curation, local dashboard, and reviewed mapping lifecycle. Six local services separate source generation, reconciliation, curation, advisory AI, mapping evaluation, and cycle coordination.

Each mutable field has its own precedence clock. A newer non-empty assertion replaces an older one; source arrival order is not the decision rule. Composite finding identities keep distinct package versions separate.

Service-owned databases avoid cross-service writes. Mapping candidates are declarative data, evaluated against golden cases and freshly checked before human-approved activation. The optional AI gate is advisory and cannot change records, policies, or approved mappings.

Retained local verification notes cover contract cases, rejected input with no partial mutation, duplicate-safe replay, reversed arrival order, mapping evaluation, review, and rollback. Requirements map to behavior checks; that mapping is distinct from line or branch coverage.

The website demonstration exercises a deliberately small illustration of precedence, replay, provenance, and mapping history. It does not execute the private connector or replace its verification suite.

The implementation makes reconciliation and controlled change inspectable: follow a projected record to its source, reproduce the processing decision, and review a mapping before changing active behavior.

The source observations are synthetic. This is a single-tenant local reference implementation, not validated vendor detection or production infrastructure.

Evidence curation and mapping evolution do not train model weights or generate and execute arbitrary code. Production identity, transport security, independent audit storage, and operational hardening remain separate work.

The diagram, interactive example, and implementation account are public. The source and retained local check records were reviewed for this portfolio; private code, operational records, and notification destinations are not published.