Inventory Web Properties Skill

← Operations Web Function

Inventory Web Properties Skill

CANDIDATE CANDIDATE NEW BOUNDED TASK · Operations Web Function 0.1.0. Build and reconcile the authoritative registry of domains, subdomains, environments, owners, lifecycle, critical paths, hosting, DNS, repositories, analytics, access-policy references, and monitoring coverage. Use when a fleet count conflicts, a property is added or retired, coverage is unclear, a monitor roster may be stale, or another Web Function job needs a trustworthy denominator.

Canonical owner: operations-web-function:inventory-web-properties · Task registration: TASK_LIBRARY_REGISTRATION_PENDING

Broader definitive hub · Exact Task Library page: TASK_LIBRARY_REGISTRATION_PENDING

Download the complete plugin · Source skill SHA-256: 1a153471f6a7e3deb56661c43c32dc7b6a7c50aa75599110ef373500ff7e5faf

Candidate source: dennisyu/blitzmetrics-skills · commit: PENDING_MERGE · path: skills/inventory-web-properties/SKILL.md

The registry answers “what do we own, who owns it, what must work, and which projection includes it?” A hosted-domain list, publishing target list, access register, analytics property list, and monitor roster can have different valid denominators. Do not force them into one unexplained count.

Build the registry

  1. Enumerate candidate sources and identify their authority, purpose, update mechanism, and freshness.
  2. Normalize each target to a stable property ID and canonical URL.
  3. Verify identity with a second attribute when names or domains can collide.
  4. Record environment and lifecycle: candidate | active | maintenance | retiring | retired.
  5. Record accountable owner, critical paths, expected statuses, service levels, and access-policy reference.
  6. Link hosting, DNS, repository, CMS, analytics, Search Console, tag manager, forms, and monitoring by references—not secrets.
  7. Reconcile contradictions at the source. A note that one list is wrong is not a correction.
  8. Generate purpose-specific projections such as hosted, publish-to, monitor, measure, and access-review from the registry.
  9. Record selected / declared, excluded items with reasons, source hashes, and timestamps.
  10. Emit property.added, property.retired, or reconciliation findings when state changes.

Honesty rules

  • A source that failed to load contributes UNKNOWN, not zero rows.
  • A stale roster cannot produce an unqualified green fleet result.
  • Every partition has a residual bucket: declared − union(classified buckets) must be empty or loud.
  • A parser that returns zero from a non-empty source is a hard failure until explained.
  • Retired properties remain in history with retirement evidence; they do not vanish.
  • Current state and append-only history are separate artifacts.

Definition of Done

  • one authoritative registry exists;
  • every active property has owner, lifecycle, canonical URL, and critical paths;
  • all source counts reconcile or have explicit, owned contradictions;
  • generated projections state their selection rule and timestamp;
  • freshness thresholds and next reconciliation are recorded;
  • downstream monitoring, access, and publishing jobs consume projections rather than private hand-maintained copies.

From the plugin root, use schemas/property.schema.json and schemas/property-registry.schema.json as the portable record shapes and route access gaps to $govern-web-access.

This is a generated candidate implementation page, not automatically a definitive article or accepted Task Library task. It delegates to the named canonical owner until reviewed registration and merge receipts exist.

Scroll to Top