Central Wiki.js space for profile novel_writing_lora.
remote_novelremote_biryunovelautonovelInbox pages are searchable but not authoritative. Reviewed and approved states require explicit user or main-Codex review. Wiki pages never enter a LoRA dataset automatically.
This profile covers remote_novel, remote_biryunovel, and autonovel.
AGENTS.md and active story or generation contracts under /root/novel_ingestor/docs./root/biryunovel.Raw local-model prose is never story state.
novel:/root/novel_ingestornovel:/root/biryunovelD:\project\autonovel/root/novel_ingestor is not assumed to be a Git worktree. Record a manifest or database backup lineage before any approved mutation.
Before writing, retrieve the applicable work contract, characters, world rules, event timeline, chapter map, recent chapter state, and prohibited settings. If an item is missing, state the gap instead of inventing it.
raw: local Gemma or other worker draft; not authoritative.reviewed: checked for contract, continuity, style, repetition, and unsupported facts.approved: accepted final prose with explicit project and style metadata.promoted: copied to the central approved-corpus area for later deliberate ingestion.Novel LoRA and YouTube LoRA remain separate. Failed, raw, or merely reviewed text cannot enter the novel LoRA candidate corpus.
The Novel server already contains a large generation and evaluation history. This is not an empty-corpus project.
Primary locations:
/root/novel_ingestor/reports/root/novel_ingestor/storage/root/novel_ingestor/docs/research/root/novel_ingestor/novel_ingestor.dbThe first training-review tier is the explicit database relationship:
chapter_approval.approved_draft_id -> chapter_draft.id
File names such as final, candidate, approved, manuscript, or writer_surface are useful discovery signals but do not grant training approval by themselves.
The metadata-only catalog is artifacts/lora_catalogs/novel_writing_lora/catalog.json. It stores source IDs, paths, sizes, hashes, approval signals, and aggregate counts without copying manuscript text from the Novel server.
wiki/novel_writing_lora/inbox/authoredwiki/novel_writing_lora/inbox/externalwiki/novel_writing_lora/reviewedwiki/novel_writing_lora/approvedInbox files are searchable but remain unreviewed. User-authored prose may request LoRA review, but it does not become training data until provenance, deduplication, quality, and the intended dataset split are approved. External material additionally requires rights review.
Small tests create central raw artifacts only. They do not write manuscript rows, alter chapter state, trigger generation services, or change LoRA corpora. Test artifacts are removed after evidence is recorded.