Back to corpus
architecturetechnical paper candidatescore 46

LinkIt — Post-MVP Advanced Features Overview

These phases are extracted from the qr-dynamic reference implementation: - **Source Location:** `[home]/Desktop/qr-dynamic` - **Full Specification:** `[home-path]`

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Document ID:** LINKIT-PHASE-14-19 **Version:** 1.0.0 **Last Updated:** 2026-01-16 **Status:** Documentation Complete These phases are extracted from the qr-dynamic reference implementation: - **Source Location:** `[home]/Desktop/qr-dynamic` - **Full Specification:** `[home-path]` Phases 14-19 extend LinkIt with advanced dynamic link features, following a **metarecursive** design pattern where each phase builds upon the previous. | Phase | Name | Key Deliverables | Dependencies | |-------|------|------------------|--------------| | 14 | Dynamic Link Foundation | Short codes, redirects, dual URLs | MVP Complete | | 15 | Schedule Rules Engine | Timezone-aware time-based routing | Phase 14 | | 16 | Device Rules Engine | Device/browser/OS-based routing | Phase 15 | | 17 | Advanced Landing Pages | JSON content builder, 10 section types | Phase 16 | | 18 | Enhanced Analytics | Scans, views, charts, CSV export | Phase 17 | | 19 | QR Code Generation | Customizable designs, bulk download | Phase 18 | 1. **Phase N depends on Phase N-1** — Cannot implement Phase 15 without Phase 14 2. **Task N.M depends on Task N.(M-1)** — Within a phase, tasks are sequential 3. **Sub-tasks build incrementally** — Database → Service → API → UI

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.