I developed this independent project with AI assistance and synthetic data. It is not a production client implementation.

Verified portfolio · controlled source · synthetic data

Implementation
and its limits.

01 / CAPABILITIES

What is demonstrated.

Each item is visible in the portfolio experience or supported by verified project behavior.

Lifecycle control

Detect, prioritize, route and remediate, validate, and conditionally close.

Decision model

Contextual risk is measured deterministically; a separate versioned policy maps it to P0–P4 remediation urgency.

Accountable work

Owner and team resolution, routed remediation, status, and evidence context; ambiguous ownership goes to governance.

Data layer

SQLite persistence and a PostgreSQL adapter designed to isolate tenant rows.

Enterprise context

Atlas Meridian as a fictional, non-production model for applications, assets, teams, owners, and source quality.

Decision dashboard

Synthetic executive summaries, filters, trends, and work detail.

Guarded assistant

AI explains approved evidence; it cannot calculate authoritative risk, resolve ownership, or override policy.

02 / ASSURANCE

Quality gates completed before publication.

These checks support the implementation claim. They are not customer-outcome or production-reliability claims.

  • Architecture and repository-policy validationVerified
  • Production portfolio build and type checkingVerified
  • Linting and automated behavior testsVerified
  • Dependency, source, configuration, and secret checksVerified
  • Container build, scan, and application smoke testVerified
  • Responsive, accessibility, privacy, and disclosure reviewVerified
03 / ARCHITECTURE

A bounded reference architecture.

The project models source signals, normalized findings, deterministic policy, ownership resolution, remediation routing, workflow adapters, persistence, validation gates, and reporting. Atlas Meridian is the fictional enterprise context used to make applications, assets, teams, ownership, and routing concrete. Source systems remain authoritative; production integrations are extension points.

WORKING PORTFOLIO

Implemented and demonstrable

Synthetic ingestion, scoring, accountable routing, workflow state, persistence, evidence-gated closure, dashboarding, and a grounded project guide.

PRODUCTION EXTENSION

Intentionally not claimed

No real bank data, customer deployment, live telemetry, enterprise-scale benchmark, calibrated business outcome, or completed authoritative integration is represented.

04 / SOURCE MODEL

Source adapters normalize records before scoring and routing.

The public site does not claim live Prisma, Wiz, ServiceNow, Jira, CMDB, EDR, CSPM, or employer integrations. Those products represent adapter categories. The architecture keeps vendor-specific records behind normalization so the risk and routing method remains portable.

Replaceable sources

Source systems are treated as inputs behind adapters; changing a scanner or workflow tool should not rewrite the decision method.

Canonical exposure record

The architecture separates source-specific fields from normalized exposure fields used for policy, routing, and reporting.

Lineage and freshness

A production record should preserve source system, source record ID, adapter version, first and last observed dates, and last refresh time.

Data quality

Malformed records, duplicate findings, stale sources, missing ownership, ownership confidence, and conflicting classifications should surface as quality warnings, not false certainty.

05 / AI ASSURANCE

Tests for prompt overrides, unsupported claims, and failures.

Adversarial contract tests were rerun on August 21, 2026. They verify control behavior without publishing prompts, credentials, or operational internals.

Prompt-boundary attacks

Contract tests check rejection of prompt overrides, secret requests, and questions outside the project.

Unsafe action requests

The assistant has no command-execution or live-target testing tools and rejects real findings and customer data.

Grounding and provenance

Material claims require approved source markers; unsupported or malformed answers fail closed.

Failure handling

Timeouts, quota limits, unavailable models, and invalid output return bounded errors with direct sources.

06 / CONTROLLED REVIEW

Deeper review, with purpose and context.

Legitimate hiring, advisory, or due-diligence conversations can request a controlled technical walkthrough. The public portfolio intentionally does not offer a downloadable implementation repository.