Interactive Prophecy Tracking And Digital Resource Curation - Source Excerpt 04 - Roadmap and open questions

Back to Interactive Prophecy Tracking And Digital Resource Curation

Summary

This source excerpt begins near Roadmap and open questions and preserves the surrounding evidence from Antichrist.net/agent-file-handoff/Archive/2026-05-13-content-user-seo/Content/Interactive Prophecy Tracking and Digital Resource Curation.md.

**Source path:** Antichrist.net/agent-file-handoff/Archive/2026-05-13-content-user-seo/Content/Interactive Prophecy Tracking and Digital Resource Curation.md

| Tier | Suggested offer | Why it fits the model |
|---|---|---|
| Free | Public dashboard, limited watchlists, weekly digest | Builds top-of-funnel habit |
| Member | Unlimited watchlists, email or push alerts, saved dossiers, member annotations, premium briefings | Converts researchers and enthusiasts |
| Pro | Team workspaces, shared taxonomies, exportable datasets, private collections, moderator tools | Fits research groups, ministries, teachers, or journalists |
| Institutional | Consulting/custom feeds, internal dashboards, white-labeled briefings | Monetizes serious organizational use |

The most important operating metrics are not raw pageviews. They are **watchlist creation rate**, **saved dossier rate**, **alert opt-in rate**, **return frequency**, **annotation rate**, **member conversion**, and **member retention**. Those metrics reveal whether the product has become a genuine research tool or is merely attracting episodic fear-driven traffic.

## Roadmap and open questions

A realistic build path is to sequence the platform so that interpretive ambition increases only as governance and data quality improve.

| Phase | Goal | Duration | Illustrative effort and cost |
|---|---|---:|---:|
| Discovery and policy design | Taxonomy, methodology, moderation policy, source contracts, legal review | 2–3 weeks | Low-to-moderate |
| MVP dashboard | GDELT + NewsAPI ingest, themes, public dashboard, basic dossiers | 5–8 weeks | Moderate |
| Retrieval and graph beta | Hybrid search, candidate verse retrieval, editor review queue, interpretation cards | 6–10 weeks | Moderate-to-high |
| Member workflow layer | Accounts, watchlists, alerts, saved dossiers, Linkwarden integration | 4–7 weeks | Moderate |
| Public flagship features | Transparent “index” page, embeddable widget, methodology hub, newsletters | 3–5 weeks | Moderate |
| Advanced platform | Neo4j graph exploration, exports, team workspaces, institutional features | 8–12 weeks | High |

The first public launch should **not** include the clock, open community posting, or Arweave publishing. The right order is:

1. Build the dashboard and dossiers.  
2. Add human-reviewed candidate verse mapping.  
3. Add member watchlists and collaborative curation.  
4. Add the public index or clock only after methodology trust is established.  
5. Add community features only after moderation staffing exists.

### Open questions and limitations

Some important variables remain unresolved.

The first is **editorial posture**. If antichrist.net wants to be devotional, interdenominational, academic, polemical, or culture-oriented, the taxonomy and moderation model will change materially. The second is **source licensing**. The technical feasibility of ingestion is clear, but the exact republication and storage rights for article bodies, snapshots, and annotations must be determined from vendor and publisher terms before launch. The third is **jurisdiction and entity structure**, which affects privacy compliance, subscription terms, and moderation liability. The fourth is **user role design**: a site for solo readers should feel different from a site intended for research teams, ministries, or journalists. Those questions do not undermine the concept, but they do determine whether the product feels like a trustworthy intelligence platform or an unstable niche media experiment.