In 2–3 lines, what changes across these lenses for your chosen tech?

Map the genealogy: TA → ELSA → RRI

Where does risk concentrate first for GPT in service contexts — data, model, workflow, or deployment?

From your tech’s supply chain, which hotspot is most sensitive in S-LCA and why?

Name one, then suggest a mitigation you’d actually implement.

What’s the first HRIA red flag in your dataset?

Early signal often appears at data ingestion/labeling drift before model usage spikes.

Where does risk concentrate first for GPT in service contexts — data, model, wor

Industrial Policy for the Final Frontier

Structuring Markets for Strategic Quantum Innovation

Implementing RRI & sustainability assessment

Technology Assessment in Practice and Theory

Responsible Research & Innovation — policy issue

Technology Assessment for Responsible Innovation

A HRIA of Digital Activities — Intro

Anticipatory governance & moral imagination

HRIA for AI Data-Intensive Systems

AI Ethics IA via Requirements Engineering

Solar Geoengineering: History, Methods, Governance

Anticipating governance in synthetic biology

Ethical Landscape of Robot-Assisted Surgery

RRI — anticipation & methods (Handbook chapter)

S-LCA in Circular Economy

Social LCA as a resource for RRI

Military & Security Dimensions of Quantum Technologies

Systematic Review of AI Impact Assessments

Ethics of Social Robotics

Future & Ethical Perspectives of Robotics/AI

Responsible Innovation as inspiration for ELSA

Integration scaffolds and coaching prompts

Peer Week Integration Kit

Peer review prompts and method clinic guidance

Policy Lab Facilitation Notes

Towards Earth–Space Governance in a Multi-Planetary Era

Evolving Governance in the Space Sector

Seminar: TA → ELSA → RRI

HRIA & Surveillance Matrix

Real-Options: Quantum/Space

Collaborative Policy Lab II (Peer Week)

Final Stakeholder Briefings

Methods Lab: Scanning & Signals

Workshop: AI Impact & Scenarios

Rapid HTA Studio: Bio/Neuro

Backcasting Clinic: Climate/Geoeng

Collaborative Policy Lab I

Energy Transition: S-LCA Exercises

Mini-Delphi: Dual-Use Governance

Speculative Vignettes: Care Robots

Survey of AIIA tools and scoring approaches

AI Impact Assessments landscape

Classical TA (expert input for MPs)

Co-construction with developers & researchers

Constructive TA (shape design)

Evidence-based HRIA framing for data-intensive systems

Human Rights Impact Assessment for AI

Using S-LCA for grid and hydrogen choices

Social LCA for energy transitions

Methods, governance debates, and contested timelines

Solar geoengineering — history & governance

PEST/STEEP framing and clustering practices

Horizon scanning & weak signals

Citizen and stakeholder involvement in appraisal

Participatory TA (broaden debate)

Stage-gates, option value, wildcard testing

Quantum & space governance uncertainty

Distribution of benefits/risks in assistive robotics

Ethics of embodied AI in care

Week 1 — Foundations: TA, ELSA/ELSI, RRI

Week 10 — Data governance, privacy, surveillance

Real-options thinking + wildcard stress-tests

Week 11 — Frontier uncertainty: quantum, space, dual-use

Week 12 — Mini-project / Peer week

Week 13 — Final synthesis & stakeholder briefings

Horizon scanning, weak signals, STEEP/PEST

Week 2 — Scanning methods & futures tools

Week 3 — Generative AI & automation

Week 4 — CRISPR, genome editing, neurotech

Week 5 — Climate interventions & geoengineering

Week 6 — Collaborative Policy Lab

Week 7 — Energy transition

Week 8 — Synthetic biology & biosecurity (dual-use)

Week 9 — Robotics, embodied AI, care & work

# Process Notes Summary

Living documents captured in `/process` — read these for context on how ideas evolved.

**Sources**
- `process/claude_thread.md` — AI partner chats about “make it cool” architecture & magic moments.
- `process/grk.md` — Core principles (session-as-container, grid composer, universal blocks, progressive disclosure).
- `process/Lisdat.md` — Unified schema blueprint + terminology (Space/Group/Section/Session/CalendarEvent).
- `process/pre3.md` — Session model proposal with phased enhancements.
- `process/pre3a.md` — Deep dive into Collection vs Session vs Agenda vs Calendar confusion.

## Highlights

### claude_thread.md — Magic + AI framing
- Start from the “wow moment” for each persona (mom’s voice button, agency drag/drop, learning community timeline).
- AI-first architecture: every node can store AI-extracted summaries, links, action items; autopilot recipes come later.
- Reinforces Assistant → Copilot → Autopilot ladder.

### grk.md — Core principles
- Sessions are universal work containers with focus modes (deep-work, exploration, collaboration, tidy-up).
- Grid composer = structured canvas that mixes signals, workflows, AI cells. Keep it visual like Figma but executable.
- Universal blocks with slash commands; blocks can reference other nodes (`@`, `[[ ]]`).
- Node/edge model keeps relationships flexible; props remain JSON for future facets.

### Lisdat.md — Schema blueprint & terminology
- Final terms: Space ▸ Group ▸ Section ▸ Session. Section = data container with optional `timeline/show_on_calendar`; Session = action moment linked to Section; CalendarEvent handles the “when”.
- Assignments live in Sections with Submissions; Signals record `assigned_in_section_id` + `created_in_session_id`.
- Facet dictionary enumerates structural, temporal, compositional, informational, social, assessment, linking facets.
- UI rules: Sidebar lists Spaces→Groups→Sections; Section page shows materials/discussions/sessions/assignments; Session page shows live notes, participants, session-created signals.

### pre3.md — Session model strategy
- MVP Session = minimal typed node with `props` bag. Start shipping without schema churn.
- Phase 1 adds `session_kind`, purpose, artifacts, outcomes into `props`.
- Allows incremental feature flags without breaking legacy data.

### pre3a.md — Untangling collections vs sessions
- Collection = syllabus bucket; Session = time-bound event; Agenda = ordered list inside Session; Calendar = only the views.
- Everything can be “collected,” but we still keep distinct nouns (Assignment, Resource, Signal).
- Reinforces mental model: **data (Section)** vs **action (Session)** vs **when (CalendarEvent)**.

## How to Use
- **Product/design:** Reference these stories when writing copy or prioritizing features.
- **Engineering:** Use session model guidance when adding `session_kind`, session memory, or event tracking.
- **Docs/PM:** Link to this summary from Hub/Explainer when someone asks “Why grid composer?” or “What’s a Section vs Session?”
