Skip to main content

Roadmap

Missing pieces​

  • Verification of build, test, and artifact generation (build_verified=false)
  • Explicit CTS CLI artifacts: command contract, exit code table, JSON output schema, examples
  • Documented release checklist and artifact verification records
  • Documented help/version/error examples for automation
  • Recorded, runnable build/run/test commands in Project-README.md
  • Reconciliation of legacy manifest fields into the current manifest

Next steps​

  1. Run and verify the existing generator scripts; record commands and outputs in Project-README.md
  2. Add CTS-aligned CLI artifacts: command contract, exit code table, JSON envelope support or a documented justification for skipping it
  3. Create a short release checklist documenting artifact locations and verification steps
  4. Reconcile and import useful fields from legacy manifest entries without deleting migration evidence
  5. Mark verified artifacts (build/tests) in the manifest's verification.level, updating build_verified/tests_verified
  6. Add examples for both human and automation use (help output, a --json example, error examples)

Potential improvements​

  • --json / --format json machine-readable output following the CTS CommandOutput envelope
  • A documented command contract and exit-code table matching CTS bands
  • --dry-run or preview mode for destructive/overwrite operations
  • A small test harness validating generated derivatives and palettes
  • Auto-generate CSS variables/design tokens directly from extracted palettes for UI projects to consume

Creative enhancements (ideas on file, not committed)​

  • An interactive local desktop preview (Tauri or small web UI) to review and accept palette selections before committing derivatives
  • Semantic linkage of logos to project manifests — auto-insert logo metadata into related Aptlantis manifests
  • Automatic favicon and multi-resolution icon bundle generation for Android/iOS/Windows/Linux
  • A palette-based theming exporter emitting ready-to-use CSS/SCSS/Tailwind config from palette files
  • Integration with a local dataset registry to tag and version logo inputs (provenance for DALL·E sources)
  • Generated accessibility metadata — contrast checks and suggested accessible foreground/background pairings per logo