generated from coulomb/repo-seed
Optional JSONPath query/extract support, FTS5 section/block search, mkt cache query and search. Local SQLite backend now supports parsed snapshot persistence, incremental refresh, cached querying, and ranked full-text search
This commit is contained in:
@@ -31,6 +31,19 @@ Build or refresh the local index:
|
||||
mkt cache index docs workplans --root .
|
||||
```
|
||||
|
||||
Query indexed snapshots:
|
||||
|
||||
```text
|
||||
mkt cache query 'sections[heading=Decision]' --root .
|
||||
mkt cache query '$.headings[*].text' --engine jsonpath --root .
|
||||
```
|
||||
|
||||
Search indexed section/block text:
|
||||
|
||||
```text
|
||||
mkt search SQLite --root .
|
||||
```
|
||||
|
||||
Inspect a parsed AST without using the cache:
|
||||
|
||||
```text
|
||||
@@ -71,6 +84,7 @@ The first schema stores:
|
||||
- `blocks`: block type, text, source span, and heading level
|
||||
- `dependencies`: reserved dependency edge table for references,
|
||||
transclusion, literate chunks, and future invalidation graphs
|
||||
- `search_units`: FTS5 virtual table over sections and blocks
|
||||
|
||||
This is enough to recover the useful markitect-main idea of keeping parsed
|
||||
structure available for faster and richer query backends, while keeping the
|
||||
@@ -78,10 +92,6 @@ normal CLI usable without a cache.
|
||||
|
||||
## Future Work
|
||||
|
||||
`MKTT-WP-0007` still needs:
|
||||
|
||||
- JSONPath query adapter over stored or live document JSON
|
||||
- FTS5 search over section/block rows
|
||||
- cache-backed query commands
|
||||
- richer dependency extraction from references, transclusion, and literate
|
||||
chunks
|
||||
Follow-on backend work can now focus on richer dependency extraction from
|
||||
references, transclusion, and literate chunks; access-controlled query gateways;
|
||||
and larger-scale memory/context packages.
|
||||
|
||||
@@ -33,7 +33,7 @@ and descriptions mirror the operational view.
|
||||
| `MKTT-WP-0003` | complete | done | `MKTT-WP-0001`, `MKTT-WP-0002`, `MKTT-WP-0004` | Core toolkit implementation is complete. |
|
||||
| `MKTT-WP-0006` | complete | done | `MKTT-WP-0004`; task-level trigger: `MKTT-WP-0003-T005` | Optional backend fabric is complete: manifests, capabilities, snapshot identity, interfaces, registry, provenance, and read-only CLI scaffolding. |
|
||||
| `MKTT-WP-0010` | complete | done | `MKTT-WP-0004`; task-level trigger: `MKTT-WP-0003-T006` | Content references, processors, explode/implode, weave/tangle, content classes, and migration examples are complete as the first WP-0010 extension layer. |
|
||||
| `MKTT-WP-0007` | P2 | todo | `MKTT-WP-0006` | First practical cache backend use case: AST/JSONPath/SQLite/FTS. SQLite snapshots, AST inspection, metadata indexing, and incremental refresh are in place; JSONPath, FTS, and cache-backed query remain. |
|
||||
| `MKTT-WP-0007` | complete | done | `MKTT-WP-0006` | Advanced query and local index backend is complete: AST inspection, optional JSONPath, SQLite snapshots/metadata, FTS5 search, incremental refresh, and local index CLI. |
|
||||
| `MKTT-WP-0005` | P2 | todo | `MKTT-WP-0003`, `MKTT-WP-0004` | Pick up when generation/form/context or semantic assessment pressure appears. |
|
||||
| `MKTT-WP-0011` | P2 | todo | `MKTT-WP-0003`; task-level triggers: `MKTT-WP-0010-T001`, `MKTT-WP-0010-T005` | Declarative Markdown dataflow workflows: source extraction, deterministic/assisted processing, and multi-output generation. |
|
||||
| `MKTT-WP-0009` | P2 | todo | `MKTT-WP-0006` | Establish access-control gateway before security-sensitive cache/context use. |
|
||||
|
||||
Reference in New Issue
Block a user