Native Markdown writing and knowledge workspace for iOS, iPadOS and macOS 27. The Mac target uses SwiftUI/AppKit with shared document, export, AI and CloudKit components. Internal Swift module names use Skriptum; the app is named Scriptum. Canonical repository: GodModeAI2025/Scriptum.
Licensed under Apache 2.0, with third-party notices in docs/licenses.
Scriptum is under active development. Its scope includes Spaces/pages, source-preserving writing, images/tables, revisions/recovery, export themes, writing assistance, iCloud collaboration and scheduled work. Feature implementation, native acceptance and delivery are tracked separately:
- Binding requirements and professional writing scope
- Current release status and retained acceptance evidence
- Release preflight
- Native Mac build 10 delivery, Mac UI verification, iOS build 9 evidence, feedback plan and Mac acceptance scope
- Privacy policy drafts — German and English
- Apple submission and German/English App Store drafts
Library sync uses iCloud/CloudKit. There is no required custom workspace-storage service. OpenAI/Anthropic API keys, authorised ChatGPT access and Apple PCC are separate optional AI connections. Live access, regional availability, provisioning and current-source TestFlight delivery require their own evidence. PDF export uses the semantic renderer in the ordinary export flow. See the current release status for its tested scope.
To import Markdown with local PNG/JPEG images, choose Markdown mit Bildern importieren, select its containing folder, then choose the documents. The text remains byte-exact; images are copied into the library and shared by preview and export. Extracted Markdown/image ZIPs can use the same import. Image paths outside the selected source, network images and ambiguous filenames are rejected with an explanation. Libraries and native packages using original image paths require the updated reader on every device; older builds fail closed. Import/export verification and limits.
| Path | Purpose |
|---|---|
Sources/ |
Native app and shared Swift components |
Tests/ |
Root Swift package tests |
Modules/ |
App-linked scheduling, writing-quality and workspace-client components |
Research/ |
Isolated, non-shipping collaboration and workspace-service prototypes |
Config/, Brand/ |
App configuration and brand assets |
project.yml |
XcodeGen source of truth |
Skriptum.xcodeproj/ |
Generated native Xcode project |
scripts/ |
Release verification and its Python tests |
docs/ |
Product requirements, legal text, licensing and retained QA/release evidence |
Server/WritingQuality/ |
Historical LanguageTool research; excluded from the Apple-only grammar product route |
GitHub serves only as the code repository. GitHub Actions is disabled; builds, tests, release verification and delivery run locally through the development tools. Retained verification evidence lives in docs/.
Use Xcode 27 and XcodeGen. Regenerate the project after changing project.yml:
xcodegen generate
xcodebuild -project Skriptum.xcodeproj -scheme Skriptum -sdk iphonesimulator -destination 'generic/platform=iOS Simulator' CODE_SIGNING_ALLOWED=NO build
xcodebuild -project Skriptum.xcodeproj -scheme SkriptumMac -destination 'platform=macOS' CODE_SIGNING_ALLOWED=NO build
swift test --disable-sandbox --scratch-path /private/tmp/ScriptumTests --no-parallel
python3 -m unittest discover -s scripts/tests -vThe Swift package builds shared components and selected model files. App UI and app resources build through Xcode. Expensive or live opt-in tests declare their environment flags in the relevant test and QA report.
Local build/dependency caches and credentials are ignored. QA captures, PDFs, images, logs and receipts under docs/ are retained as evidence, with their documented scope and dates.
Historical reports retain their original paths and hashes. The current mapping for relocated prototypes is documented in Research; the native target and root package do not compile those prototypes.