IntentGuard

IntentGuard Weekend MVP — Development Specification

Authoritative specificationspecificationml

Source of truth

Part of docs/specification/ — the repository declares this tree the sole authoritative design source. The README and backlog do not override it.

Status: Specification complete; implementation not started.

IntentGuard is a local-first support-intent classifier that compares a TF-IDF logistic-regression baseline with a fine-tuned DistilBERT classifier and can abstain when model confidence is below a validation-derived threshold.

The repository is intentionally scoped to a 12–16 hour weekend implementation on one laptop. It demonstrates production ML judgment through an end-to-end pipeline, honest evaluation, input validation, focused tests, latency measurement, and a small FastAPI inference boundary.

Scope-frozen vertical slice#

  1. Download and validate BANKING77.
  2. Train and evaluate the classical baseline.
  3. Fine-tune and evaluate one DistilBERT classifier.
  4. Select an abstention threshold from validation data.
  5. Serve POST /v1/predict and GET /health.
  6. Run focused tests and generate a comparison report.

Nothing else belongs to the guaranteed MVP.

Source of truth#

Read these documents in order:

  1. Project brief
  2. Requirements and acceptance criteria
  3. Architecture
  4. ML system design
  5. Implementation plan
  6. Scope control
  7. Agent operating guide

Supporting documents:

Planned implementation commands#

These commands are contracts for the implementation; they are not claims that the application already exists.

make setup
make data
make baseline
make train
make evaluate
make test
make serve

The primary demonstration path will be:

make setup data baseline train evaluate test
make serve

Honest status#

CapabilityStatus
Architecture and requirementsDocumented
Dataset pipelinePlanned
Baseline modelPlanned
DistilBERT modelPlanned
Abstention policyPlanned
FastAPI servicePlanned
Automated testsPlanned
Measured model resultsNot yet available

No accuracy, F1, calibration, latency, user-impact, or production-usage claims should be added until they are generated by the reproducible evaluation pipeline.

Related in repository

Open in full graph →
LINKS_TOLINKS_TO — source: README.mdLINKS_TOLINKS_TO — source: docs/OPERATIONS.mdLINKS_TOLINKS_TO — source: docs/specification/README.mdLINKS_TOLINKS_TO — source: docs/specification/README.mdLINKS_TOLINKS_TO — source: docs/specification/README.mdLINKS_TOLINKS_TO — source: docs/specification/README.mdLINKS_TOLINKS_TO — source: docs/specification/README.mdLINKS_TOLINKS_TO — source: docs/specification/README.mdLINKS_TOLINKS_TO — source: docs/specification/README.mdLINKS_TO — source: README.mdLINKS_TO — source: docs/OPERATIONS.mdLINKS_TO — source: docs/OPERATIONS.mdCURRENTdocument: IntentGuard Weekend MVP — Development SpecificationIntentGuarddocument: IntentGuardOperationsdocument: OperationsProject Briefdocument: Project BriefRequirements and Accepta…document: Requirements and Acceptance CriteriaMinimal Architecturedocument: Minimal ArchitectureML System Designdocument: ML System DesignWeekend Implementation P…document: Weekend Implementation PlanScope-Control Systemdocument: Scope-Control SystemAGENTS.mddocument: AGENTS.md
Hover an edge for its provenance · click a node to open it10 nodes · 12 edges