Initial Read Protocol

Protocol Overview

When you enter a site cold — no prior context, no knowledge layer, no session history — this protocol gives you a reliable sequence for building a mental model before taking any action. It covers four domains in order: system health, content structure, active plugins, and theme context.

The order matters. Site health first because it tells you what's broken. Content structure second because it defines the terrain. Plugins third because they reveal capabilities and dependencies. Theme last because it's the most stable and least time-sensitive.

The Protocol

1. 1
   Site Health Check

   Get the overall site health status and run a pulse check. This surfaces critical issues before you touch anything else.

   site-health/statussite-health/pulse
2. 2
   Discover Post Types

   List all registered post types. This shapes everything downstream — you need to know what kinds of content exist before you can query them.

   content/discover-types
3. 3
   Map Content Structure

   Get the site map (page hierarchy) and list top-level post counts by type. Do not read post content yet — structural metadata only.

   content/get-site-mapcontent/list-structure
4. 4
   Audit Active Plugins

   List all installed plugins, noting which are active. This reveals what modules are available and which Fluent suite products are in play.

   plugins/list
5. 5
   Read Taxonomy Structure

   List categories and tags in use. The term counts tell you where content is concentrated.

   taxonomies/discovertaxonomies/list-terms
6. 6
   Survey Theme Context

   Get the active theme and its design snapshot. Note the block theme status — this determines whether Blocks module or Theme module abilities are relevant.

   themes/get-activethemes/design-snapshot
7. 7
   Check Abilities Suite Status

   If the Knowledge Layer is active, run knowledge/boot for a site-aware orientation document. Check suite status for enabled modules.

   suite/get-statusknowledge/boot

Pacing Note

The pacing rule is not a performance constraint — it's an accuracy constraint. When you fire abilities in rapid sequence without reviewing each result, you build a model on top of unread data. The model becomes confident about things you haven't actually seen.

After each step, ask: What did this change about my understanding? If the answer is nothing, something went wrong — either the ability returned unexpected data or you didn't read the result.

All Abilities Used

Related