Document intake and curation workspace for the Quack.com archive project.
New material lands in incoming/, gets processed here, and then moves into
historic/ folders organized by type.
Drop unsorted captures, scans, PDFs, screenshots, and notes into the intake folder first so nothing gets lost while we are still identifying what it is.
public/quack/incoming/As each document is understood, we extract dates, context, and summaries, then decide which historic lane it belongs in.
Settled material moves into typed folders that can later support public exhibits, timelines, and demo reconstructions.
public/quack/historic/Interviews, recollections, milestone notes, and narrative fragments that preserve the human story around the company.
public/quack/historic/memories/Reconstructed experiences, audio flows, and presentation material that help the original product feel tangible again.
public/quack/historic/demos/Primary-source documents such as screenshots, scans, press coverage, diagrams, and photos.
public/quack/historic/artifacts/Recovered source, technical notes, dependency clues, and restoration experiments needed for preservation or replay.
public/quack/historic/code/Curated Quack.com and AOL-era source list with notes about what has already been archived locally and what still needs capture.
Contains a Quack.com team photo caption and retrospective sale/product framing that help seed the historic timeline.
Provides a concise retrospective summary describing Quack.com as a pioneering interactive voice assistant acquired in 2000.
Quack and Kinitos / NeoEdge now share the same first-pass method for analyzing incoming historical material so provenance, dates, and archive-lane decisions stay consistent.
public/data/shared/incoming-artifact-analysis-playbook.mdpublic/data/shared/incoming-artifact-analysis-template.mdThe repository now matches the intended intake-to-history flow.
incoming/.historic/.