Internal system

Editorial generation from facts and relationships

Status: registry snapshot · sources checked

State: The C4 record dated 22 Oct 2026 accepts the transferred development CMS baseline with a known language-metadata failure. It does not accept the full iWriter generation system; the record stops work after C4 at the owner’s request.

Next action: Use C4 as evidence about the development CMS; scope full generation acceptance and the next stage separately.

Unknown: Generation completeness is unverified. The 12 Oct report is not a current whole-project verdict; model comparisons do not prove publishing readiness.

Snapshot: 2026-10-23T16:03:03.353969+00:00

Game layer, retention and monetization

Status: registry snapshot · not rechecked live

State: Wiki, media and design located; current-game reconciliation incomplete

Next action: Reconcile wiki/landing with accepted game state and clarify discrepancies

Unknown: Unknown: which mechanics are actually released

Snapshot: 2026-10-21T23:20:15.577Z

Creator acquisition: verified contacts, tasks, outreach and replies

Status: registry snapshot · sources checked

State: The README describes Telegram PR Agent, AI Shift Lead, Task Factory and automatic collection of Telegram Business replies in the pilot. Its header says verified 8 Sep, its Git revision is 15 Sep and the local project revision is 26 Sep; the journal separately records funnel work on 21 Oct. These are distinct evidence points, not a verified deployed version.

Next action: Reconcile README, journal and deployed versions, reply capture, RLS and current funnels; do not launch outreach.

Unknown: Current version, operators, Telegram Business/Instagram and RLS unknown. Reconcile README limits; do not waive them

Snapshot: 2026-10-23T16:03:03.353969+00:00

Website and shared platform

Status: registry snapshot · sources checked

State: The development CMS has C4 technical acceptance dated 22 Oct 2026: save, review, release and new-version readback. Language metadata still fails. This does not accept all website or production features.

Next action: Reconcile the site map with C4 technical acceptance and module journals; do not generalize it to the whole product.

Unknown: Traffic and metrics: S09; values not retrieved

Snapshot: 2026-10-23T16:03:03.353969+00:00

Social layer, authors and subscriptions

Status: registry snapshot · not rechecked live

State: Direction approved; implemented features need reconciliation

Next action: Reconcile Owner-described funnels with current PR Agent templates and Task Factory

Unknown: Author growth, retention and follows: methodology pending

Snapshot: 2026-10-21T23:20:15.577Z

Status: registry snapshot · summary only

State: P0/P1: internal map and links; product research later

Snapshot: 2026-10-21T23:20:15.577Z

Status: registry snapshot · summary only

State: Do not carry source order forward; separate facts from hypotheses

Snapshot: 2026-10-21T23:20:15.577Z

Status: registry snapshot · summary only

State: DeFight is game/monetization/retention layer, not a creator replacement

Snapshot: 2026-10-21T23:20:15.577Z

Status: registry snapshot · summary only

State: Further languages follow audience research

Snapshot: 2026-10-21T23:20:15.577Z

Status: registry snapshot · summary only

State: Batch 5 and discuss one at a time. Blocking questions immediately; no weekly schedule

Snapshot: 2026-10-21T23:20:15.577Z

Status: accepted · owner decision

State: Internal wiki on Docusaurus and Markdown. Reuse the future dapp.expert author editor instead of building a separate editor.

Snapshot: 2026-10-22

Status: registry snapshot · summary only

State: Root checks revision and log; other agents submit proposals

Unknown: Decision summary; full source is referenced in the registry.

Snapshot: 2026-10-21T23:20:15.577Z

Status: accepted · owner decision

State: Before building a module, find existing components, assess suitability, reuse or adapt. Build new functionality only for a confirmed gap.

Snapshot: —

Status: accepted · approved in brief

State: Each record has one editing authority. A snapshot shows its source, revision and date. Unknown is not zero; a plan is not a working feature.

Snapshot: —

Status: accepted · catalog checked

State: A reference view of existing catalogs, not a replacement inventory. Applicability is task-specific.

Snapshot: 2026-10-22

Discover existing solutions

Status: registry snapshot · sources checked

State: The catalogue links existing solutions and the C09 development pipeline. A listing does not prove tool access for every executor.

Next check / use: Select relevant materials before each task; see C09 for the pipeline and the planned documentation-update handoff.

Unknown: Reference rather than duplicate catalog

Snapshot: 2026-10-23T16:03:03.353969+00:00

Prepare bounded tasks

Status: registry snapshot · not rechecked live

State: Mandatory knowledge_review before Aider

Next check / use: DE2 / implementation under profile rules

Unknown: Read selected materials, not whole archive

Snapshot: 2026-10-21T23:20:15.577Z

Search and source reading for AI

Status: registry snapshot · sources checked

State: The README describes DeepSeek with search and page reading, with local and server installations. The application journal records Kopilka use. Current settings and access from other environments were not checked.

Next check / use: iWriter source research; PR Agent research/enrichment — candidates

Unknown: Documents disagree on limits. The effective cap is unverified; no numeric cap is asserted here. Each installation and client has its own settings. Each installation is accessed through its own loopback; Railway cannot directly reach the computer’s loopback. High-volume sourcing for PR Agent is not authorized.

Snapshot: 2026-10-23T16:03:03.353969+00:00

Collect ideas, research and exchange

Status: registry snapshot · sources checked

State: The Kopilka README documents finding intake, an evaluation queue, Google Docs results and a Claude, OpenAI and DeepSeek cascade. This is an architecture description, not a new live bot test.

Next check / use: Shared research; assess utility per project

Unknown: The deployed version and cross-environment access are unverified. Kopilka settings and quotas cannot be assumed for other projects.

Snapshot: 2026-10-23T16:03:03.353969+00:00

Execution and independent acceptance

Status: registry snapshot · not rechecked live

State: Codex; Claude subscription; DeepSeek via approved route

Next check / use: Current pilot: Codex + Claude

Unknown: Subscription quota differs from API; GLM planned

Snapshot: 2026-10-21T23:20:15.577Z

Assess block state and growth

Status: registry snapshot · not rechecked live

State: Read-only GA4/GSC connector; Yandex/custom counters unreconciled

Next check / use: Website, content, game, creators: assessment candidates

Unknown: Unknown metrics must not become zero

Snapshot: 2026-10-21T23:20:15.577Z

Design, assets and changes

Status: registry snapshot · not rechecked live

State: Archive located; figma-sync registered in catalog 22 Oct

Next check / use: dapp.expert / DeFight; other uses unreconciled

Unknown: Account-specific access; schedule conflict: README 05:00 vs catalog 09:00. Actual schedule unverified

Snapshot: 2026-10-21T23:20:15.577Z

Storage, runtime and recovery

Status: registry snapshot · sources checked

State: The wiki runs over HTTPS with temporarily password-free access and noindex at the owner’s request. A private GitHub source copy and recovery of 85 source files were verified on the same computer.

Next check / use: Restore password protection on a separate owner request. Verify recovery on another computer and total infrastructure costs separately.

Unknown: Noindex is not access control. One wiki check does not verify all servers or backups; recovery on an independent computer remains untested.

Snapshot: 2026-10-23T16:03:03.353969+00:00

Execute approved tasks with separate review and acceptance

Status: registry snapshot · sources checked

State: The devpipeline exists. Its README documents executors, separate review, acceptance checks and a queue. The journal records build stages 0–2 accepted on 22 Oct 2026. In the separate readiness initiative, stages 1–2 were accepted on 23 Oct 2026 and stage 3 was in progress as of 23 Oct 2026, 18:47 Moscow time.

Next check / use: Owner plan: hand documentation auto-updates to the pipeline. The handoff and automatic updates have not been implemented.

Unknown: Documented features do not imply that every integration is ready. Wiki integration, update sources, allowed changes and acceptance need a separate stage.

Snapshot: 2026-10-23T16:03:03.353969+00:00