📖About

Human visit stats only count browser page-loads; readers who consume the Logbook/Carolopedia through AI chatbots are invisible, though their crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, meta-externalagent, etc.) do fetch pages and land in nginx access logs. Add an AI Readers layer: (1) daily scheduled sweep parsing nginx access logs for AI-crawler user agents on public content routes (orion-logbook, carolopedia, carol bio, landing), deduped, stored in an ai_visits table beside the human visit log; (2) an admin-only read endpoint on the auth app mirroring the visit-log/all pattern; (3) an AI Readers view in the Admin Monitor: daily fetch counts by bot and top pages read, alongside the human visitor charts. Sweep registered per the scheduled-process conventions with run-audit rows.

⚖️Decisions

• Elrond's bypass methodology checklist (a reminder, not a gate -- you've got this): 0. File it requested_mode='bypass' (planner-vs-bypass is a deliberate choice). bypass_start REFUSES a non-bypass initiative (CAROL-INI-1846), and the dispatcher only skips the bypass lane when the mode says bypass -- a 'planner' mistag lets Merlin's pipeline grab the placeholder step and block your finished work. 1. Filed as planned status -- let the bypass claim/activate it; never file active. 2. Open the bypass (bypass_start) with your droid id + the remediation answer (remediates_initiative_id=NNN, or remediates_nothing=True). 3. Work the blocks for your work-type: template -> design -> code -> test -> review. Do the real work; record decisions on the initiative as you make them. 4. Reality is recorded for you at close -- code (files changed), each decision, and the twin-review verdict become real activities tied to this initiative and show in the Activity Tracker like a planner run (CAROL-INI-1840). No dummy rows. 5. Keep the initiative status moving; it parks in 'reviewing' and is tagged uat-pending for you at close (CAROL-INI-1836), so the stuck-watchdog leaves it alone until UAT. 6. Close runs the gates (design/architecture compliance + caller-audit). If a gate flags something pre-existing or unrelated to your change, waive it with a clear written rationale -- audit, don't skip. 7. Bypass skips the planner's auto-orchestration, NOT the standards. Same template checklist, same review, same observability as a planner run. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> blocked | event=stuck_10min_no_activity | Elrond safety net: initiative has had no activity for 10+ minutes. Blocking under the parallel safety mechanism. (el-watchdog)
• Elrond blocked initiative under the CAROL-INI-2162 dead-Albus protocol. Albus was supposed to wake for step 0 (cause=albus_no_show) but did not respond. Cause: albus_no_show. Reason: Elrond safety net: initiative stranded 10+ min. Albus wake failed or produced no useful result. (el-s1)
• [status-router] blocked -> reviewing | event=operator_put | Watchdog blocked mid-bypass close; twin review PASSED (or-rv-01), exec 559 completed - operator-correcting to reviewing/uat-pending. (orion)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> blocked | event=operator_put | PUT /api/initiatives (operator)
• [status-router] blocked -> reviewing | event=operator_put | CLI-038: 2685 twin-PASSED + uat-pending; watchdog re-struck it post-close on Jul-11 — operator-correct blocked->reviewing (standing rule) (orion)
• [status-router] reviewing -> blocked | event=operator_put | PUT /api/initiatives (operator)
• [status-router] blocked -> reviewing | event=operator_put | PUT /api/initiatives (operator)
• [status-router] reviewing -> closed | event=operator_signoff | Auto-accepted (CAROL-INI-1859): Orion-initiated, >2 days in reviewing with no objection. (el-srac-01)

✅Success criteria

• Ninad can open the Admin Monitor and see an AI Readers view showing, per day, how many pages each AI crawler (e.g. GPTBot, ClaudeBot, PerplexityBot, meta-externalagent) fetched from the public site (must_have)
• The AI Readers view lists the top pages AI crawlers read (Logbook stories, Carolopedia pages) so Ninad can see WHAT they are reading, not just how much (must_have)
• AI crawler fetches are collected automatically every day without manual action, and the collection job is visible to process monitoring like any other scheduled process (must_have)
• Human visitor numbers in the existing charts remain unchanged — AI traffic is shown as its own series, never mixed into human counts (must_have)