Project Intake - Maintain iOS

1) Executive Summary

Native iOS maintenance and habit-support app with backend coordination, treated as active but needing source-state refresh because the local branch is ahead and behind origin.

This 1079 intake treats the project as active and uses source-backed evidence rather than inferred live-product claims.

2) Project Type and Domain

• Project type: initiative
• Status: active
• Trail: TBD / untrailed
• Domains: builder, operations
• 1079 posture: First-class project intake with source-state caveat.

3) Repository and Live URLs

• Repository: maggielerman/maintain-ios
• Local source: /Users/maggielerman/Github/maintain-ios
• Live URL: Unknown unless separately documented in source files.

4) Product/User Journey Summary

The public reader should understand Maintain iOS through its source evidence, operational decisions, and artifact trail. The journey is not treated as a polished product tour unless source files and screenshots support that claim.

5) Architecture and Stack Summary

Architecture evidence comes from the source repo files listed below. The intake keeps stack claims conservative and marks any missing runtime or live URL evidence as an unknown.

6) Key Workflows and Operational Flows

• Source review and classification under Hyphenomenon project 1079.
• Human/operator review of whether this repo is active, paused, killed, or supporting-only evidence.
• Project artifact generation, validation, dry-run sync, and later apply only after status/trail metadata are preserved.

7) AI Context: Prompts, Chats, Agent Workflows

This project is part of a cross-repo AI-assisted intake batch. AI or automation claims are included only when the source repo itself documents agent, AI, automation, or workflow behavior.

8) Supporting Docs and External Resources

Hydration Source Artifacts

Source	Canonical URL	Type	Hydration value
README.md	GitHub	md	Primary source summary and workflow context.
AGENTS.md	GitHub	md	Supporting source evidence for this intake.
ROADMAP.md	GitHub	md	Supporting source evidence for this intake.
CHANGELOG.md	GitHub	md	Supporting source evidence for this intake.
DOCS/README.md	GitHub	md	Primary source summary and workflow context.
docs/README.md	GitHub	md	Primary source summary and workflow context.

9) Screenshot Gallery (with relative links + captions)

Caption: Primary source summary and project posture.

Caption: Source files, commands, and implementation structure.

Caption: Deployment, docs, automation, or runtime evidence where present.

Caption: Git/source-state evidence plus 1079 classification.

10) Candidate Import Nodes and Relationships

• Candidate project slug: maintain-ios
• Candidate project status: active
• Candidate trail: TBD / untrailed
• No explicit related project slug in this batch.
• Supporting evidence notes should preserve source excerpts, screenshots, and dry-run output.

11) Risks, Gaps, and Unknowns

• Live URL and current deployment state are unknown unless source evidence explicitly proves them.
• The source repo may have dirty state, branch drift, or stale history; this dossier records inspected state rather than claiming production freshness.
• Public representation must not promote killed or paused experiments as active work.

12) Handoff Checklist for Hyphenomenon Import

• Source artifacts created in the source repo.
• Hydration payload extracted.
• Dossier validated with required screenshots and project-page packet.
• Dry-run sync captured under DOCS/intake/1079-cross-project-intake/maintain-ios/.
• Local apply and route verification completed only after dry-run review.
• Production apply held for explicit operator approval.