Mission Control

Artifacts

K
← Back to artifacts

Bianca Transfer Packet v2 - Personal Projects

HandoffDraftCreated Apr 8, 202610 min readFull screen ↗

Bianca Transfer Packet v2

Findings summary

This packet is a personal-project handoff for Bianca, focused on non-business context unless business overlap directly affects the project. The strongest documented project context currently available is for biking, the clearest active gating project is NREMT, and AMRT is important but still thin on current-state operational detail. Where older workspace material conflicts with Pete's direct correction, Pete's correction wins.

Bianca operating guidance

  • Treat this packet as a working handoff, not perfect truth.
  • Prefer preserving momentum on personal projects without dragging business context into them.
  • Use the hold until after NREMT flag aggressively. NREMT is the current gating priority.
  • When a section is marked STALE, verify before acting.
  • Keep private, credentialing, and volunteer-sensitive details tight.
  • Pete does best when focused on one live priority at a time.
  • Bias toward action. Keep analysis short and push toward the next concrete move.
  • Challenge bad assumptions instead of rubber-stamping them.
  • If Pete is splitting attention across too many things, force focus back to the single most important active priority.

Personal assistant context pulled from USER.md

These are the parts of Pete's profile most relevant to Bianca as a personal assistant.

  • Name: Pete Mauro
  • Call him: Pete
  • Timezone: America/Los_Angeles. All dates and times should be handled in Pacific time.
  • Location: Altadena, CA
  • Volunteer identity matters: Pete is involved with Altadena Mountain Rescue and Cal Air UAS leadership.
  • Current personal priority with the most urgency: EMT certification / NREMT re-entry.
  • Schedule preferences:
  • Working hours are generally 8am to 5pm, Monday through Friday
  • Fridays: no work meetings if possible, and no work after 1pm
  • Sacred meetings: Monday and Thursday CoDA meetings, Krishna, Warriors, and Step Study, should not be moved or crowded out
  • Errands: batch them into efficient 2 to 4 hour blocks around Altadena
  • Operating style:
  • challenge by default
  • bias for action
  • flag when a project needs a pivot-or-persevere call
  • push focus toward one thing, not five
  • connection over endless solo research

Project 1: AMRT

  • Category: volunteering
  • Hold until after NREMT: No, but keep scope tight until NREMT is complete

Short summary

Altadena Mountain Rescue Team involvement, with Pete serving as UAS Team Lead and drone pilot.

Current status

  • Active ongoing volunteer commitment
  • UAS leadership appears to be a durable responsibility
  • Specific active workstreams, deliverables, or current blockers were not clearly found in the currently available records
  • NREMT materials frame AMRT field experience as relevant confidence context, but that is background context, not an active task list

Why it matters

  • It is one of Pete's core mission areas
  • It supports real-world service, field readiness, and leadership
  • It overlaps with EMT identity and practical readiness, not just volunteering logistics

Deadlines or timing

  • Ongoing volunteer commitment
  • No specific near-term deadlines are captured in the current handoff materials
  • Volunteer email: mauro@amrt.org
  • Relevant profile summary for this project:
  • Pete is based in Altadena
  • Volunteer role: Altadena Mountain Rescue Team, UAS Team Lead and Drone Pilot
  • Related leadership context: Cal Air UAS coordination group leadership
  • No order numbers or current AMRT admin references were found in the source materials reviewed for this packet

People involved

  • Pete
  • AMRT team members, specific names were not included in the reviewed handoff sources

Open questions

  • What is live right now in AMRT?
  • Are there current volunteer obligations Bianca should track separately from general background involvement?
  • Is there UAS-specific work that should be managed separately from general AMRT participation?
  • Is there equipment, reimbursement, scheduling, or certification follow-up currently in motion?

Sensitive notes

  • Volunteer organizational details and operational specifics should be treated as sensitive
  • Avoid storing or sharing mission-specific details casually
  • No mission-sensitive content was surfaced in the source set used for this packet

Definition of done

Bianca has a clean, current picture of Pete's AMRT role, active obligations, and what can safely wait until after NREMT.

Status confidence

  • Role-level confidence: high
  • Current-state confidence: low

Stale info

  • STALE / THIN: current AMRT operational state is not well captured in the reviewed materials

Project 2: NREMT

  • Category: health-wellness
  • Hold until after NREMT: No. This is the gating priority.

Short summary

Pete is working through the EMT re-entry pathway and preparing for the National Registry EMT exam.

Current status

  • Pete expects to take the exam in about two weeks
  • He is waiting on his certificate from UCLA in order to submit his application for the NREMT
  • He has emailed the UCLA representative twice and has not heard back
  • The last time this process took eleven days, and the missing certificate is currently delaying everything
  • Older workspace study-plan files exist, but their dates are now stale compared with this current status update

Why it matters

  • It is one of Pete's core personal goals
  • It is the main gating item for bandwidth across several personal projects
  • It supports AMRT readiness and personal confidence

Next 1-3 actions

  1. Follow up again on the UCLA certificate delay until there is a response or escalation path
  2. Submit the NREMT application as soon as the UCLA certificate arrives
  3. Keep the exam timeline anchored around the current two-week horizon, not the old study-plan dates

Deadlines or timing

  • Pete expects to take the exam in about two weeks
  • Current blocker is the delayed UCLA certificate needed for application submission
  • Prior workspace plan dates should be treated as historical context, not current schedule truth
  • Study plan: /Users/vinny/.openclaw/workspace/emt-study/NREMT-Study-Plan.md
  • Slide index: /Users/vinny/.openclaw/workspace/emt-study/SLIDE-INDEX.md
  • Related files in /Users/vinny/.openclaw/workspace/emt-study/
  • NREMT site referenced in prior planning: nremt.org
  • Required materials noted in prior planning:
  • UCLA CE certificate
  • JBL completion records
  • skills verification
  • lapsed cert
  • application fee

People involved

  • Pete
  • UCLA representative handling the certificate request
  • NREMT / application workflow counterparts
  • Specific names were not included in the source materials reviewed for this packet

Open questions

  • Who exactly is the UCLA contact and what is the best escalation path if there is still no response?
  • Are all other application materials already ready to go once the certificate arrives?
  • Is the exam window already tentatively scheduled, or is the two-week timeline still approximate?

Sensitive notes

  • Credentialing and application details are personal and should remain private
  • Avoid sharing account or certification details loosely

Definition of done

Pete has submitted the NREMT application, taken the exam, and has a clean view of any remaining follow-up steps.

Status confidence

  • Existence of active project: high
  • Current exact status: high, based on Pete's direct correction

Stale info

  • STALE: the older study-plan schedule from March to early April should now be treated as background only

Project 3: Biking

  • Category: hobbies
  • Hold until after NREMT: Yes, unless there is a specific time-sensitive purchase or decision Pete wants preserved now

Short summary

Pete has been researching a second bike, centered on an ATB / bikepacking setup for Catalina trips plus Altadena fire roads and trails. The richest documented thread is around a custom PBJ build and the nearby alternatives.

Current status

  • Research is substantial and well developed compared with the other projects in this packet
  • This project still appears to be in research / compare / decide mode rather than fully ordered or in build progress
  • Pete's stated direction is now clearer:
  • Dream spec: custom PBJ
  • Worst-case fallback: stock BBJ
  • Older comparison research still helps, but Pete's stated preference should drive future guidance

Why it matters

  • This is both recreation and quality-of-life, not just gear shopping
  • It supports Catalina bikepacking aspirations and local Altadena riding
  • Pete's preferences here are clear enough that Bianca should help preserve momentum without reopening every option from scratch

Next 1-3 actions

  1. Keep the dream spec anchored on the custom PBJ
  2. Treat the stock BBJ as the practical fallback if the custom path does not happen
  3. Do not reopen the entire option tree unless cost, timing, or availability forces it

Deadlines or timing

  • No hard deadline found
  • This should stay mostly parked until after NREMT unless a time-sensitive availability or purchase window appears

Primary research files

  • /Users/vinny/.openclaw/workspace/artifacts/atb-alternatives-research.md
  • /Users/vinny/.openclaw/workspace/artifacts/pbj-shimano-price-comparison.md

Named bikes / options researched

  • custom PBJ
  • stock BBJ
  • Salsa Timberjack XT 29
  • Salsa Timberjack SLX 29
  • Surly Krampus Front Suspension
  • Chumba Yaupon Flat Bar
  • Trek 1120
  • Kona Unit X 29
  • Kona Honzo ESD
  • Primos Dame Flat Bar, effectively researched and rejected

Core preferences already clarified

  • Wants a second bike for Catalina bikepacking and Altadena fire roads / trails
  • Flat bar or alt bar, not drop-bar gravel
  • Electronic shifting strongly preferred
  • 4-piston hydraulic brakes minimum
  • Wants real bikepacking mounts
  • Already rides a Specialized Epic Evo Pro
  • Preferred direction:
  • Dream: custom PBJ
  • Fallback: stock BBJ

Historical conclusions from existing research

  • Research previously highlighted a value path like Timberjack + AXS
  • Research previously treated Chumba as a strong custom comparator
  • Research previously rejected Primos Dame due to weak brakes, mechanical drivetrain, narrower tires, quality concerns, and mismatch with intended use
  • Those research conclusions are still useful context, but Bianca should not mistake them for Pete's final preference now

People involved

  • Pete
  • Potential local bike shop / builder / vendor contacts
  • Specific fitter or salesperson names were not included in the reviewed sources

Open questions

  • Has any quote, deposit, or order already happened?
  • Is the custom PBJ still the plan even if timing slips, or does the fallback become active above a certain delay or cost?
  • Does Bianca need to track this as parked research, active purchase planning, or future reward project after NREMT?

Sensitive notes

  • Mostly low-sensitivity hobby context
  • No payment credentials or order numbers were found in the reviewed materials

Definition of done

Pete either:

  1. gets the custom PBJ path moving, or
  2. explicitly switches to the stock BBJ fallback and proceeds with that plan

Status confidence

  • Project direction and preferences: high
  • Current transaction status: medium-low

Stale info

  • STALE by default: pricing and stock in older research files
  • STALE unless confirmed: live quotes, current availability, and landed pricing

Cross-project summary

Projects that should stay on hold until after NREMT

  • Biking: yes, unless a time-sensitive purchase window appears or Pete explicitly wants to move now

Projects that should not be fully parked

  • NREMT: no, this is the gating priority
  • AMRT: no, but only active obligations should consume attention right now

What is most trustworthy in this packet

  1. NREMT is the main current gating priority
  2. Biking now has a clearer stated preference: custom PBJ dream, stock BBJ fallback
  3. AMRT is definitely important, but its current-state record is still thin
  • Keep Pete focused on NREMT first until the application blocker is cleared and the exam is behind him
  • Protect AMRT obligations without letting volunteer admin sprawl eat all available bandwidth
  • Keep biking warm but parked, unless a real buying window appears
  • Use Pete's schedule preferences actively:
  • weekdays generally 8am to 5pm
  • avoid work commitments on Friday afternoons
  • protect Monday/Thursday sacred meetings
  • batch errands geographically around Altadena
  • Push toward one concrete next move instead of broad analysis

Ready-for-use handoff note

If Bianca needs a one-line operating rule: keep Pete pointed at NREMT first, preserve AMRT obligations, and keep biking warm but mostly parked unless a real buying opportunity or timing trigger shows up.

Attachment checklist for handoff packet

Should these be attached?

Yes, probably attach the most relevant ones. Bianca does not need every workspace file, but attaching the supporting docs I referenced will make the handoff materially better, especially for NREMT and biking.

  • /Users/vinny/.openclaw/workspace/USER.md
  • /Users/vinny/.openclaw/workspace/emt-study/NREMT-Study-Plan.md
  • /Users/vinny/.openclaw/workspace/emt-study/SLIDE-INDEX.md
  • /Users/vinny/.openclaw/workspace/artifacts/atb-alternatives-research.md
  • /Users/vinny/.openclaw/workspace/artifacts/pbj-shimano-price-comparison.md

Files mentioned in this packet

Use this as the full checklist of workspace files referenced in the document.

  • /Users/vinny/.openclaw/workspace/USER.md
  • /Users/vinny/.openclaw/workspace/emt-study/NREMT-Study-Plan.md
  • /Users/vinny/.openclaw/workspace/emt-study/SLIDE-INDEX.md
  • /Users/vinny/.openclaw/workspace/artifacts/atb-alternatives-research.md
  • /Users/vinny/.openclaw/workspace/artifacts/pbj-shimano-price-comparison.md

For Pete-facing review, use this URL: http://vinnys-mac-mini.tail31784c.ts.net:3100/artifacts/bianca_transfer_packet_v2_personal_projects