Architecture blueprint and workplan refinement
This commit is contained in:
parent
228b397fc5
commit
9f1b8da87a
10 changed files with 539 additions and 1 deletions
|
|
@ -30,6 +30,13 @@ Primary: FR-020 to FR-030.
|
|||
Supporting: FR-001 to FR-008, FR-022 to FR-028, FR-200 to FR-202,
|
||||
FR-240 to FR-244.
|
||||
|
||||
## Architecture Constraint
|
||||
|
||||
Implement ingestion through connector and extractor ports described in
|
||||
`docs/architecture-blueprint.md`. Format-specific parsing, local filesystem
|
||||
access, `markitect-tool`, PDF/document libraries, and dataset readers must live
|
||||
behind adapters, not in the domain core.
|
||||
|
||||
## I6.1 - Implement ingestion job model status and retry surface
|
||||
|
||||
```task
|
||||
|
|
@ -168,4 +175,5 @@ Acceptance:
|
|||
- Local file, text, markdown, PDF/document placeholder, and dataset ingestion
|
||||
scenarios are covered by tests.
|
||||
- Job status and provenance are inspectable through programmatic APIs.
|
||||
- Connector and extractor boundaries follow `docs/architecture-blueprint.md`.
|
||||
- `python3 -m pytest` passes.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue