PhyloMosaicA STEMsaic Research Impacts product

Partnership evaluation, in the browser

The record of a partnership, kept where the work happens

Capture what partners make and say. Check in on health and goal alignment each period. Read the pieces as a timeline, a mosaic and a map, and generate the report from the same record.

Home: current partnership status Artifact with tagged passages Check-in matrix Mosaic clustering Sociogram Generated progress check
Home: current partnership status, findings and partner health

Five options

Pick the one that fits the work. Each option sets up its own goals, codebook, check-in rhythm and data pathway. Each has a how-to deck that walks through a demo workspace step by step, and the demo opens in the app with one click.

How it works

Four tabs in the sidebar, one record underneath. Everything on the Understand and Share tabs reads what the Collect tab holds.

Artifacts list

Collect

Artifacts (photos, notes, transcripts, slips, documents) and check-ins, entered live, by link, or imported from a CSV.

Mosaic view

Understand

Timeline, mosaic, sociogram and dashboards filter by who, what, where and how. Sample sizes show on every figure.

Goal tree

Direct

A goal tree with owners and status, the codebook with definitions and change history, and the log of findings and recommendations.

Reports

Share

Five editable report drafts, a REFI-QDA project for NVivo or MAXQDA, CSVs, and the AI kit for work you do outside the app.

Safety defaults

The app runs in your browser and stores its data there. Nothing is sent to a server unless you set up hosting for your group.

Your browser holds the data

The workspace lives in this browser's storage. A passphrase lock encrypts it at rest. Download a backup file after every session; the home page reminds you when one is due.

Students by code only

In an evaluation workspace, students appear by study code or analysis id. Consent gates what counts, and small groups are suppressed on every dashboard.

Adults named with agreement

Roster people appear by role on maps and in exports until they agree to be named. The data pathway card records who approved what, and where each data class may live.

AI stays outside

The app never calls an AI. You export the schema and prompts, do that work where your governance allows, and import the result for row-by-row review.