Week 1 Overview
Dates: [Start Date TBD]
Focus: Platform Onboarding & Technical Foundations
Phase: 1 of 4 (Technical Foundations & Regulatory Mapping)
Week 1 Objectives
By the end of Week 1, you should:
- Have full platform access - Development environment, API credentials, collaboration tools
- Understand IntegrityStudio’s architecture - High-level grasp of OpenTelemetry-based observability platform
- Attend your first engineering standup - Begin integration with the engineering team
- Start regulatory research - Initial review of EU AI Act technical requirements
- Establish working relationships - Meet all key supervisors and mentors
- Set up your documentation workflow - Personal notes system for learning and research
Day-by-Day Breakdown
Monday: Orientation & Access Setup
Morning (9:00 AM - 12:00 PM)
- Welcome meeting with Alyshia Ledlie (CEO)
- Review internship objectives and expectations
- Discuss IntegrityStudio’s mission and product vision
- Clarify communication preferences and availability
- Complete HR/administrative onboarding
- Sign any required agreements (NDA, IP assignment, etc.)
- Set up payroll/timekeeping (if applicable)
- Review company policies
Afternoon (1:00 PM - 5:00 PM)
- Development environment setup
- Install required software (see Onboarding Checklist below)
- Configure Git and clone relevant repositories (read access)
- Set up local development tools
- Communication tools setup
- Slack workspace access and channel overview
- Notion workspace access (or equivalent documentation platform)
- Calendar integration and meeting scheduling
- Review IntegrityStudio platform overview documentation
- High-level architecture diagrams
- Product feature overview
- Customer use cases
End of Day Deliverable: Access confirmed for all tools; environment setup complete
Tuesday: Platform Deep Dive & Supervisor Meeting
Morning (9:00 AM - 12:00 PM)
- Meeting with John Skelton (Head of Policy)
- Discuss legal/regulatory guidance expectations
- Review Phase 1 regulatory research scope
- Understand existing compliance documentation
- Clarify your role in policy-engineering bridge
- IntegrityStudio platform walkthrough
- Request demo environment access
- Navigate the UI and core features
- Understand the data flow: traces, metrics, logs
Afternoon (1:00 PM - 5:00 PM)
- Begin OpenTelemetry learning
- Read: OpenTelemetry Concepts Overview
- Watch: OpenTelemetry introductory videos (if available)
- Take notes on: signals (traces, metrics, logs), context propagation, instrumentation
- API documentation initial review
- Locate IntegrityStudio API documentation
- Understand authentication mechanisms
- Identify compliance-related endpoints
End of Day Deliverable: Complete first set of OpenTelemetry learning notes; platform access confirmed
Wednesday: Engineering Team Integration
Morning (9:00 AM - 12:00 PM)
- Attend first engineering standup (observer)
- Note: Observe team dynamics and development workflow
- Learn current sprint priorities
- Identify compliance-related work in progress
- Meeting with Minea Arkiomaa (Head of AI Compliance Development)
- Discuss technical compliance implementation approach
- Review existing compliance features in the platform
- Understand her expectations for your technical contributions
- Identify pairing session opportunities
Afternoon (1:00 PM - 5:00 PM)
- Continue OpenTelemetry learning
- Focus: Trace data model and span attributes
- Focus: Metrics types (counters, gauges, histograms)
- Focus: Log signal and correlation with traces
- Review IntegrityStudio codebase (read-only)
- Understand directory structure
- Identify compliance-related modules
- Note questions for engineering team
End of Day Deliverable: Attended first standup; documented initial codebase observations
Thursday: Regulatory Research Kickoff
Morning (9:00 AM - 12:00 PM)
- EU AI Act technical requirements review
- Read Articles 6-7 (Risk Classification)
- Read Article 9 (Risk Management System)
- Read Annex IV (Technical Documentation Requirements)
- Begin mapping to observability concepts
- Meeting with Micah Lindsay (Chief Data Scientist)
- Discuss AI evaluation methodology
- Understand how IntegrityStudio measures AI system performance
- Learn about existing evaluation metrics in the platform
Afternoon (1:00 PM - 5:00 PM)
- Begin Regulatory-to-Observability mapping document
- Create initial document structure
- Draft EU AI Act requirements summary
- Start mapping documentation requirements to OpenTelemetry signals
- Attend engineering standup (if scheduled)
- Review national AI guidance documents
- German BfDI resources (primary language advantage)
- Bookmark AEPD (Spain) and CNIL (France) for later review
End of Day Deliverable: Initial draft of Regulatory-to-Observability mapping structure
Friday: Week 1 Wrap-Up & Planning
Morning (9:00 AM - 12:00 PM)
- Complete Week 1 learning documentation
- Finalize OpenTelemetry notes
- Document platform architecture understanding
- Compile questions that arose during the week
- Week 1 review meeting with supervisor(s)
- Share progress on objectives
- Discuss challenges and blockers
- Clarify expectations for Week 2
Afternoon (1:00 PM - 5:00 PM)
- Prepare Week 2 plan draft
- Based on Week 1 learnings and feedback
- Identify specific engineering pairing opportunities
- Plan regulatory research priorities
- Self-assessment
- What went well?
- What needs more time?
- What support is needed?
- Submit any required weekly reports/timesheets
End of Day Deliverable: Week 1 summary notes; Week 2 draft plan; all access/setup issues resolved
Onboarding Checklist
Accounts & Access
| Item | Status | Notes |
|---|---|---|
| IntegrityStudio email/SSO | [ ] | |
| Slack workspace | [ ] | |
| GitHub organization | [ ] | Read access to repos |
| Notion/documentation platform | [ ] | |
| IntegrityStudio demo/staging environment | [ ] | |
| API developer credentials | [ ] | |
| Calendar access | [ ] | |
| Video conferencing (Zoom/Google Meet) | [ ] |
Development Tools
| Tool | Status | Purpose |
|---|---|---|
| Git | [ ] | Version control |
| VS Code (or preferred editor) | [ ] | Code/doc review |
| Python 3.x | [ ] | API integration examples |
| Node.js | [ ] | SDK examples (if applicable) |
| Postman/Insomnia | [ ] | API testing |
| JSON Schema validator | [ ] | Schema development |
| Markdown editor | [ ] | Documentation writing |
Documentation Access
| Resource | Status | Location |
|---|---|---|
| IntegrityStudio API docs | [ ] | |
| Platform architecture docs | [ ] | |
| Compliance feature specs | [ ] | |
| Engineering team wiki | [ ] | |
| Previous compliance research | [ ] |
Learning Resources for Week 1
OpenTelemetry Fundamentals
- OpenTelemetry Concepts - Start here
- OpenTelemetry Signals Overview - Traces, metrics, logs
- OpenTelemetry Data Sources - Instrumentation patterns
- Semantic Conventions - Attribute naming standards
IntegrityStudio Resources
- Platform product overview (request from team)
- API documentation (location TBD)
- SDK getting started guide (location TBD)
- Customer case studies (if available)
EU AI Act Technical Requirements
- EU AI Act Full Text
- Articles 6-7: Risk classification system
- Article 9: Risk management system requirements
- Annex IV: Technical documentation requirements
- European Commission AI Act Overview
National Regulatory Guidance
- German BfDI AI guidance (German language)
- AEPD (Spain) AI guidance (Spanish language)
- CNIL (France) AI guidance (French language)
- UK ICO AI and data protection guidance (English)
Key People to Meet
| Person | Role | Meeting Purpose | Scheduled |
|---|---|---|---|
| Alyshia Ledlie | CEO | Strategic vision, internship objectives | [ ] Monday |
| John Skelton | Head of Policy | Legal/regulatory guidance, research scope | [ ] Tuesday |
| Minea Arkiomaa | Head of AI Compliance Development | Technical compliance implementation | [ ] Wednesday |
| Micah Lindsay | Chief Data Scientist | AI evaluation methodology | [ ] Thursday |
| Engineering Lead (TBD) | Platform architecture | Codebase overview, API questions | [ ] Week 1-2 |
Questions to Ask Each Person
Alyshia Ledlie:
- What does success look like for this internship?
- What are the most urgent compliance challenges customers face?
- How should I balance technical learning with regulatory research?
John Skelton:
- What existing regulatory analysis can I build upon?
- Which jurisdictions are highest priority for customers?
- How should compliance research be documented and shared?
Minea Arkiomaa:
- What compliance features are currently in development?
- How can I best support the technical compliance work?
- What engineering pairing sessions would be most valuable?
Micah Lindsay:
- How does IntegrityStudio currently evaluate AI systems?
- What metrics are most important for compliance monitoring?
- What gaps exist between legal requirements and current capabilities?
Week 1 Deliverables
| Deliverable | Due | Status |
|---|---|---|
| Development environment fully configured | Monday EOD | [ ] |
| All accounts/access confirmed | Tuesday EOD | [ ] |
| OpenTelemetry learning notes (initial) | Wednesday EOD | [ ] |
| First engineering standup attended | Wednesday | [ ] |
| Regulatory-to-Observability mapping (initial structure) | Thursday EOD | [ ] |
| Week 1 summary document | Friday EOD | [ ] |
| Week 2 draft plan | Friday EOD | [ ] |
Questions to Answer / Research to Begin
Technical Questions (Week 1)
- How does IntegrityStudio collect and store observability data?
- What OpenTelemetry signals are currently supported?
- How do customers authenticate to the API?
- What compliance features already exist in the platform?
- How are traces correlated with metrics and logs?
Regulatory Questions (Week 1)
- What specific EU AI Act articles require audit trails?
- How does risk classification translate to documentation requirements?
- What are the technical documentation requirements in Annex IV?
- How do national implementations differ from the EU AI Act?
- What timelines apply for high-risk AI system compliance?
Integration Questions (Week 1)
- How can observability data satisfy EU AI Act documentation requirements?
- What gaps exist between current platform capabilities and compliance needs?
- What API endpoints would be needed for automated compliance reporting?
- How should audit trails be structured for arbitration readiness?
Notes Section
Use this section to capture observations, learnings, and ideas throughout Week 1.
Monday Notes
Date:
Key learnings:
Questions that arose:
Action items:
Tuesday Notes
Date:
Key learnings:
Questions that arose:
Action items:
Wednesday Notes
Date:
Key learnings:
Questions that arose:
Action items:
Thursday Notes
Date:
Key learnings:
Questions that arose:
Action items:
Friday Notes
Date:
Key learnings:
Questions that arose:
Action items:
Week 1 Reflection (Complete Friday)
What went well this week?
What was challenging?
What support do I need going forward?
Key insights about the platform/company
Adjustments needed for Week 2 plan
This document is a working guide for Week 1. Update checkboxes and notes sections as you progress. Bring this document to your Friday review meeting to discuss progress and plan Week 2.
Related Documents:
- Technical & International Arbitration Track Capstone Proposal
- Week 2 Plan (to be created)
Contact:
- Supervisors: John Skelton, Minea Arkiomaa
- CEO: Alyshia Ledlie
- IntegrityStudio: sales@integritystudio.ai