All runbooks
surveyuai-explorerredacted view

Zenbook Survey Summary

Synced UAI Explorer survey documentation from docs/surveys/zenbook-2026-06-20-summary.md.

Updated 2026-06-21·Freshness: Reference·Sensitive tokens or credentials were hidden before display.

Zenbook Survey Summary

Date: 2026-06-20
Device: Zenbook
Host observed: zenbook-14
Status: metadata inventory complete

Access Outcome

SSH BatchMode access to scott@10.0.0.107 succeeded and the target reported hostname zenbook-14. The survey used the non-root scott account only.

The survey stayed metadata-only: no remote folders were mounted, no raw source files were copied, no file contents were quoted, and production CT 121, sandbox CT 126, DNS, TLS, firewall, reverse proxy, and public routes were not mutated.

Survey Scope

  • Roots checked: Documents, Desktop
  • Existing roots without matching docs: Documents
  • Matching root: Desktop
  • Max depth: 5
  • Candidate docs seen: 107
  • Recorded metadata rows: 105
  • Secret-adjacent aliases suppressed before artifact output: 2
  • Inventory truncated: no

Counts By Project Or Topic

Project or Topic Candidate Files
AI delegation notes 33
Cadence 6
Cadence/UAI Orb 7
Cortex/Skipper operations 23
Desktop documentation candidates 9
Devine 1
Infrastructure operations 12
UAI 4
Verification and reports 10

Counts By File Type

File Type Candidate Files
md 71
txt 18
tsv 8
pdf 5
html 3

Notable Candidate Areas

  • AI delegation and handoff notes look like the largest documentation cluster.
  • Cortex/Skipper operations and verification reports are substantial enough to justify a separate review lane.
  • Cadence, Cadence/UAI Orb, Devine, and UAI material are present and should be reviewed for standards, lineage, and freshness before promotion.
  • Infrastructure operation notes are metadata-visible but should stay in a restricted review queue until redaction and operator review are complete.

Raw Survey Lineage

  • Manifest: [REDACTED:high-entropy].json
  • Inventory: [REDACTED:high-entropy].csv
  • Previous blocked report retained: [REDACTED:high-entropy].md

Next Steps

  1. Review metadata aliases for non-public or stale material before selecting any files for redaction.
  2. Run a redaction/classification worker only on selected candidates in the raw survey zone.
  3. Promote only sanitized summaries, approved excerpts, tags, freshness state, and lineage metadata into the public Explorer catalog.
  4. Keep secret-adjacent suppressed aliases out of public artifacts unless they go through a private manual review lane.