Portfolio pilot — records and evidence
Portfolio pilot — records and evidence
Date: 2026-09-23. Execution: lip-tqk.10. Read/update walkthrough completed with Rufus on 23 September 2026. Wider import is now unblocked. This is a five-record sample, not the full portfolio.
Read the sample
| Record | Current lifecycle | Owner | Next milestone / reason for inclusion |
|---|---|---|---|
| Project-management infrastructure | In progress | Rufus | Reconciled inventory and initiative queries; sample walkthrough complete |
| Seeds brand rollout | In progress | Unconfirmed | Rollout confirmed underway; integrate newer work, superseding old deferred notes |
| Life Itself | Unknown / source activity unverified | Unconfirmed | Top-level source record needed to resolve the sample hierarchy |
| Second Renaissance | Unknown / source activity unverified | Unconfirmed | Nested initiative with current project context and historical naming |
| 2R Newsletter | Paused | Unconfirmed | Planned transition to Canto with a smaller role; parent confirmed as the Seeds/Second Renaissance work |
An unknown owner/status means this migration has not confirmed it, not that the activity or its leadership does not exist. The broader current planning view remains the roadmap. Other files have not yet been converted or declared inactive.
Source coverage and mappings
Read Tao's 45-entry portfolio/index.js snapshot at commit 7eb1f0753c8c5faea256f8b44ce9f55a12f9cfe1, current repository project files, and bounded spreadsheet ranges Programs!A1:V100 and Projects!A1:U120. This is sample discovery, not a full spreadsheet audit; later rows, hidden tabs and additional document contents were not inspected for this pilot.
| Source entry | Destination / disposition |
|---|---|
Tao life-itself | initiatives/life-itself.md; root preserved, historical owner/activity kept in evidence |
Tao second-renaissance; Programs row 47 | initiatives/second-renaissance.md; common parent retained, creation date preserved |
| Projects row 105, ID 2402, “Second Renaissance” | Candidate accounting/programme match linked from the initiative; not duplicated as a bounded project |
Tao second-renaissance-newsletter; Programs row 46 | initiatives/second-renaissance-newsletter.md; source parent conflict exposed, current parent left null |
| Projects row 108, ID 2502, “Seeds of a Second Renaissance Newsletter” | Possible related delivery project or duplicate publication entry; linked as unresolved, not merged as fact |
Existing projects/2606-seeds-of-renaissance-brand-rollout.md | Adapted in place; body and source links retained, old status line preserved in dated note and explanation |
Existing projects/2605-project-management-infrastructure.md | Adapted in place; current execution evidence recorded; no owner inferred from Rufus's authorisation |
Source links with tab/row references are in the individual records. No source spreadsheet or Tao file was changed. No financial data was imported into the portfolio.
Beads association sample
Added initiative:second-renaissance to existing programme root lip-42k, and project:2606-seeds-of-renaissance-brand-rollout to existing rollout epic lip-42k.2. Existing labels are preserved; neither change creates a standing initiative Bead. Rollout child lip-42k.2.1 remains without either new label, demonstrating why a direct-label lookup is insufficient.
Existing standalone lip-9vh carries initiative:studio. Its corresponding initiative slug/name must still be reconciled; it was not silently relabelled to the source's sensemaking-studio. This provides a standalone association case and an explicit unmatched-label case without inventing work. Production membership queries remain lip-tqk.11.
Verification evidence
Core documentation and skill checks are recorded in skill adaptation validation. The real sample is checked for parseable frontmatter, required metadata, legal lifecycle/phase values, unique slugs, resolvable acyclic parent links, local Markdown links and existing Bead references. Existing project prose is compared with the pre-migration version after accounting for the status line moving into metadata.
Temporary copies exercise update, pause and close operations: append dated notes, distinguish tickler/review from due date, preserve sources and parent links, and retain the closed record. These are technical checks only; no real project or initiative is falsely paused or closed.
Coordination-team walkthrough
One available member of Rufus/Fae/Asdra should use the table/linked records to find a project's current position, owner, next milestone and task route, then request or make a supported correction using the documented workflow. An AI-assisted correction counts as the agreed update route; mere generation of a sample by an agent does not demonstrate a person's experience.
Useful concrete corrections include confirming the infrastructure project's owner, clarifying whether the rollout is currently executing or still deferred, or resolving the newsletter's parent/status. Only apply information actually supplied. Record participant, correction, resulting edit and any difficulty finding the information. A source conflict can remain unresolved if the walkthrough demonstrates the route without guessing it away.
Result: passed through the agreed AI-assisted route. Rufus reviewed the inline summary and supplied corrections: he owns infrastructure, rollout is underway, and the newsletter is paused within the Seeds work with a planned shift to Canto and a smaller role. Those corrections were applied to the records and read back. Usability feedback was substantive: keep plans in docs/plans, show main review points inline rather than temporary-worktree links, and give current confirmation precedence over outdated April material. This is evidence of the chat-assisted route, not a claim that Fae/Asdra independently tested Git editing or cloud Beads access.
