NoiseProof Agent Proof Surface - 2026-06-01 refresh
NoiseProof Agent Proof Surface - 2026-06-01 refresh
이 artifact는 svy04/noiseproof-agent public repo가 어떤 증거를 남겼는지와, 그 repo가 아직 증명하지 못하는 것을 분리한다.
목적은 “AI agent를 완성했다"는 주장이 아니다.
허용되는 주장은 더 작다.
NoiseProof Agent는 지저분한 시장 데이터 문제를 evidence-first RAG/Agent workflow로 작게 쪼개고, 각 gate를 문서, 테스트, CI, runbook, proof path, application package로 남긴 public portfolio artifact다.
Claim
svy04/noiseproof-agent는 Day 1 documentation-first package에서 시작해 service skeleton, profiler, parser, chunking, lexical retrieval, collection plan, Evidence Ledger, Noise Gate, claim-bounded report preview, operations dashboard, persisted proof records, workflow-parent lineage, failure-case persistence, application-ready review, external-reader proof path, external reviewer brief, Braincrew role map, and portfolio-site handoff review까지 공개 repo에 남겼다.
이 사실은 “inspectable portfolio artifact"를 지지한다.
이 사실만으로 production RAG quality, real customer validation, semantic retrieval quality, robust PDF extraction, hosted deployment, market prediction quality, trading advice capability, Braincrew acceptance는 증명되지 않는다.
Source Snapshot
| source | observed through | evidence |
|---|---|---|
| svy04/noiseproof-agent | public GitHub repo | Public repo exists with README, docs, API app, packages, tests, CI, Docker Compose DB target, proof path, and application package. |
| External-reader proof path | repo proof index | Shortest repository-native path for a reviewer. |
| External reviewer brief | reviewer-facing brief | Two-minute path for a reviewer before leaving feedback. This is request infrastructure, not feedback itself. |
| External review issue #1 | GitHub issue | Public request surface for bounded feedback. As of this refresh, no external reviewer comment is counted. |
| Live route verification | blog proof artifact | Confirms the public blog route serves the latest NoiseProof proof markers and reviewer route refresh. |
| Application package final consistency review | review artifact | README, proof path, portfolio index, application-ready review, and Braincrew role map are internally consistent. |
| Portfolio site handoff review | review artifact | Decides to refresh this existing portfolio proof artifact instead of creating a broad marketing page. |
Commit e99875f | Git commit | External reviewer live proof route refresh added and pushed to main. |
CI run 26722211291 | GitHub Actions | docs: link external reviewer live proof route completed successfully on main. |
Previous proof marker 3dfe5e4 | Git commit | External reviewer brief was the previous public proof marker before the route-refresh gate. |
Evidence Map
| area | artifact | allowed claim |
|---|---|---|
| Problem framing | README, product brief, ADRs | NoiseProof is not a trading bot; it is a market-intelligence evidence workflow. |
| Service boundary | FastAPI app, PostgreSQL schema, Docker Compose, CI | local service shape and persistence boundary exist. |
| Input handling | fixtures, Document Profiler v0, parser adapters | messy inputs can be profiled and parsed through explicit warning/failure boundaries. |
| Chunk/retrieval preview | chunk strategy experiment, lexical retrieval | fixed-window, heading-aware, row-aware chunking and lexical source-id retrieval can be compared. |
| Collection planning | Collection Plan Preview | required information roles are planned before evidence ledger work. |
| Evidence/report gates | Evidence Ledger, Noise Gate, report preview | unsupported claims and buy/sell drift are blocked by deterministic preview gates. |
| Operations surface | ops summary/dashboard, run traces, warning codes | local metadata and proof records are inspectable through plain API/dashboard surfaces. |
| Failure proof chain | failure-case persistence, workflow parent linkage, fresh DB dashboard proof | manual failure-case provenance can be persisted and surfaced; automatic failure-case creation is not claimed. |
| Application package | portfolio index, application-ready review, Braincrew role map | FDE-first application narrative is mapped with claim boundaries. |
| External reader path | external-reader proof path, external reviewer brief, and final consistency review | a reviewer can follow a compact proof path without reading every phase log. |
| External feedback request | issue #1 and feedback intake criteria | the repo has a public request surface for critique; feedback remains pending until an outside reviewer leaves a substantive comment. |
Current Verification
Observed in the noiseproof-agent repo before this portfolio refresh:
uv run pytest -q
uv run python -m compileall app ../../packages/ingestion
docker compose config --quiet
git diff --check
Latest local test result for the current NoiseProof proof marker:
189 passed, 1 warning
Observed remote CI before this artifact refresh:
CI success on e99875f / run 26722211291
This portfolio refresh itself is not hosted deployment evidence for NoiseProof. It only updates the public proof surface on this blog.
Fresh public route verification for this blog proof surface is recorded separately at NoiseProof Live Route Verification - 2026-06-01.
Claim Boundary
Allowed public claims:
- NoiseProof Agent is a public portfolio repo.
- It is FDE-first and Product Engineer-secondary in its application framing.
- It demonstrates an evidence-first workflow from input profiling to report preview.
- It blocks unsupported claims and buy/sell drift in deterministic preview gates.
- It has CI, Docker Compose DB target, runbook, evaluation docs, role map, application-ready review, external-reader proof path, external reviewer brief, public review issue, and portfolio handoff review.
Forbidden public claims:
- Do not claim it is production-ready RAG.
- Do not claim robust PDF extraction.
- Do not claim semantic retrieval or embeddings.
- Do not claim real customer validation.
- Do not claim hosted deployment.
- Do not claim automatic failure-case creation.
- Do not claim complete workflow failure causality.
- Do not claim market prediction quality.
- Do not claim trading advice or buy/sell recommendation capability.
- Do not claim Braincrew acceptance or external hiring validation.
- Do not claim external reviewer feedback until an outside reviewer leaves a substantive evidence-referenced comment.
Next Artifact
The next proof should not be a larger claim.
It should be one of:
- external reviewer feedback on issue #1,
- a local or hosted demo transcript with screenshots,
- or a follow-up implementation phase that turns more manual proof handoffs into inspectable runtime paths without claiming production quality.