28 lines
630 B
Markdown
28 lines
630 B
Markdown
# FAQ
|
|
|
|
## Why add a review UI?
|
|
|
|
Because automatically generated packs are draft assets, not final trusted assets.
|
|
|
|
## What can a reviewer change?
|
|
|
|
In this scaffold:
|
|
- concept trust status
|
|
- prerequisites
|
|
- titles
|
|
- descriptions
|
|
- merge/split intent records
|
|
- conflict resolution notes
|
|
|
|
## Is the UI fully interactive?
|
|
|
|
Not yet. The current version is a static HTML scaffold backed by real JSON data models.
|
|
|
|
## Why keep a review ledger?
|
|
|
|
To preserve provenance and make curation decisions auditable.
|
|
|
|
## Does promotion mean certification?
|
|
|
|
No. Promotion means "reviewed and improved for Didactopus use," not formal certification.
|