Walk a pin through with Clara. She probes the reasoning, then structures it into claims.
Pin queue
Morning Check-in
Started 7:48 AM · still open to add to
Clara
Good morning, Zoltan. Before we get into the day — anything settle in your mind overnight from yesterday's architecture review or the conversation with clinical leadership?
Zoltan · 7:46 AM
Yeah. The audit-trail granularity question from the bed-management conversation is still working at me. I think procurement is going to push back on the scope adjustment but the right move is to surface the patient-safety frame before we even open that thread.
Clara
Got it. That maps to the conversation pattern you've described before — surface the safety rationale first. I'll tag this to clinical-engineering partnership and we can walk it through with the others when you percolate.
Zoltan · 7:48 AM
Good. Let me get into the day.
Clara
All good. I'll be here when something pings — pin it anytime.
Reopen the check-in any time — add a thought and Clara folds it into today's record.
Clara consolidates your pins at end of day. You don't have to be polished.
Photo
Text
Video
Captured today
Percolate
Yesterday's pins · Step 1 of 4
roleup
ZB
Tools
Week 4 outputs · Refreshing as your graph grows
Clara assembles these from your captured knowledge across the four-week engagement. Each gets richer as more is captured. Below: a preview of what's emerging from your current capture state.
Onboarding brief
For a senior engineer joining your team
Generated from 24 patterns · 6 of 7 categories · Updated just now
View brief
Workaround & relationship cascade
What breaks first if you're not in the room
Preview available · Full assessment in Week 4 output
Preview
Decision territory map
Visual representation of how your domains connect
Preview available · Full version in Week 4 output
Preview
Team onboarding deck
Slide-format version of your architectural reasoning
Architectural philosophy at Providence
The hybrid cloud decision framework
Clinical-engineering partnership patterns
What I'd tell my successor
Preview available · Full version in Week 4 output
Preview
Anomaly stream
What's not matching what we believed — running delta
Azure Key Vault permission boundary — recurring
2×
CST Cerner adapter drift from reference architecture
1×
Procurement bypassing clinical preview
1×
5 flags across 3 days · 1 recurring pattern
Preview
ZB
Zoltan Bozoky
Director of Software Engineering Providence Health Care
PHC-12847 · BOUND 2020-06-15
Role context
DepartmentDigital Health & Information Technology
LocationVancouver, British Columbia
PortfolioEngineering platform across acute care and integrated digital health
Seat numberseat_DSE_PHC_0001
Practitioner typeExpert (primary binding)
Tenure6 years
EngagementDay 15 of 29
Responsibilities & skills
Responsibilities
The macro accountabilities of your role, drawn from your job description and confirmed during intake.
Skills
The capabilities you apply across your responsibilities. Each pin Clara captures attaches to one responsibility and one skill — that's how the OLG keeps two axes of structure.
How this was built. Initial scaffolding seeded from your job description on Day 1. Confirmed during a 30-minute intake with Bruce on Day 2 — you adjusted three skill names and added "Stakeholder communication" as a distinct capability. Clara will refine this over time as your work surfaces new patterns.
Teams
Digital Health Engineering — Providence
Functional · Lead
Clinical-Engineering Partnership Forum
Cross-functional · Member
CanDIG Federated Genomics Alumni Network
Community · Member
Settings
NotificationsDaily summary at 6:30 PM
Voice captureEnabled
Knowledge sovereigntyPersonal copy retained
Data residencyBritish Columbia
ROLEUP · v0.9 PILOT · ABRAXIS INC
roleup
ZB
Review
Claims Clara structured from your percolations. Release each to the org when it reads true to you.
3
Ready for your review
21
Released to org
Ready for your review
Released to the org
How release works
RoleUp surfaces. You decide. Nothing reaches the organization's graph until you release it.
Captured patterns
Clara is composing your brief
Home
Review
Tools
Profile
Released to the org
Now in Providence's knowledge graph.
Edit pin
Pin text
Category
Photos & video
Edit claim
Claim
Category
Context tag
Workaround & relationship cascade
Critical · Single-point failure, no redundancy
High · Operationally degrades within days
Moderate · Continuity erodes over weeks
Workaround and relationship cascade map — shows what fails first if you're not in the room, including both manual operational fixes and single-point-of-access relationships. The full assessment is part of your Week 4 output and includes operational risk scoring, relational dependency mapping, and prioritized remediation suggestions.
Decision territory map
Full mind map available as Week 4 output — generates dynamically from your captured graph across all seven categories. Node size reflects claim density; line weight reflects observed cross-domain decision overlap.
Team onboarding deck
Architectural philosophy at Providence
The hybrid cloud decision framework
Clinical-engineering partnership patterns
What I'd tell my successor
Full slide deck available as Week 4 output — generates from your captured knowledge across all seven categories. Each slide cites underlying claims and is editable before export.
Anomaly stream
5 flags across 3 days · grouped by pattern
Anomaly stream surfaces flagged deltas grouped by pattern — never auto-resolves, never asserts truth. Accountability for what to do about each pattern stays with the practitioner and their supervisor. Full assessment in Week 4 output includes cross-practitioner pattern detection where multiple roles flag related observations.