Documentation

Concepts

The vocabulary — every artefact is a node in one linked study. Open a concept for its data schema.

PersonasFoundation

A synthetic customer with a SOUL (who they are) and a growing memory of everything they've been through. Not a static profile — it remembers and evolves.

Why it mattersAnswers come from lived experience and shift over time, instead of repeating the same line.
View schema →
JobsContainer

The container for one study — a question, from open exploration to a clear answer. Everything belonging to that question lives here.

Why it mattersOne place to see what's done and what's open — and how each piece feeds the outcome.
View schema →
CouncilsEvidence

A memory-grounded debate where personas react to a question, a concept, or a decision — each speaking from its own memory.

Why it mattersReal, traceable reactions instead of opinions: any statement leads back to the memory behind it.
View schema →
ReferencesEvidence

A website, external prototype or A/B variant as a stimulus — with capture status and a snapshot when available.

Why it mattersPersonas react to real material, not a retelling. References are links/snapshots, not uploaded files and not a test result; the result lives in a council or session.
More →
PrototypesEvidence

A testable project object — app, flow, dashboard, cards, comparison, model or journey — that Sonaloop can run, render and connect to sessions.

Why it mattersGrounded reactions to something real, not a description — you see what works before you build.
View schema →
SessionsEvidence

A replayable usage trace: what the persona saw, did, thought and decided — as a screen walkthrough, clickable prototype or live surface.

Why it mattersIt shows behavior and friction, not just a final opinion.
More →
SurveysEvidence

A sendable instrument with questions and options; real responses can be imported and read against persona predictions.

Why it mattersIt quantifies open tensions instead of leaving them only qualitative.
More →
Cloud_githubEvidence

A Cloud automation that turns GitHub PRs, issues, comment commands and preview deployments into Sonaloop reaction tests, then writes results back as a Check Run, comment, label or Patch PR.

Why it mattersUser reaction moves directly into the development workflow: landing pages, feature issues and UI changes get a persona-grounded signal before they ship.
More →
AssetsEvidence

A real file in the project: screenshot, document, export or generated deliverable — with provenance, direction and download.

Why it mattersAssets are the material behind evidence, walkthrough screens and deliverables. They are files, not council references.
More →
NoteEvidence

A lightweight idea or observation captured anywhere in a study — from a raw observation to a worked-out solution idea.

Why it mattersThe lowest-friction way to keep a signal you can later test in a council or turn into a prototype.
View schema →
SectionStructure

A simple grouping of related items in a study — a cluster, a theme, a phase.

Why it mattersStructure however the findings naturally group — without forcing a rigid template.
View schema →
HypothesesOutcome

A falsifiable bet: expected metric or direction, confidence, and later the observed value.

Why it mattersIt separates assumptions from outcomes and makes learning auditable.
More →
DecisionsOutcome

A decision record: what was chosen, which evidence supports it, and which alternative was rejected.

Why it mattersThe handoff from research to action remains traceable.
More →
ReportsOutcome

The answer — key problems and recommendations, and/or a narrative, presentation-grade write-up of the whole study.

Why it mattersPresentation-grade and PDF-exportable — and itself citable evidence that can feed a larger study.
View schema →
Data modelFormat

How everything is stored as JSON: three layers and the five shared primitives every artefact is composed of.

Why it mattersUnderstand the data format — and export/integrate with confidence.
View the format →
open

Feedback

Sent along, transparently: Page · Version 0.2.0

Or open a GitHub issue ↗