Platform

The platform layer of an iOS + macOS app, done by editing its Xcode project, shipped as a Granite agent package: Info keys and URL schemes, App Transport Security, entitlements and the macOS sandbox, the app delegate, macOS menu commands, and app extensions (an Action or Share extension with its app group, and the inbox the app reads what it left from). A call says what the app needs in a few short lines; the package edits project.pbxproj as text, merges into the Info.plists and entitlements already there, and writes the Swift the app answers with.

It is one of the Rao Craft Agents: independent packages that, tagged in prompts along the life of a project, build an app of Loom's quality. platform is Loom's AppDelegate, its two Info.plists and entitlements, and its Action/SetInstance extension, said generally.

How an app finds it

PlatformAgent is a GraniteAgentPackage, and it carries a record in its binary:

@used @section("__DATA_CONST,__granite")
let platformRecord: GraniteRoster.Record = { GraniteRoster.record(PlatformAgent.self) }

In Craft, install it from the Agent Store or with craft agents add https://github.com/Rao-Craft-Agents/PlatformAgent.git, then say $platform in a request:

$platform the recipe app takes photos of dishes, opens recipes:// links, lets people save a link or
a photo to it from the share sheet, and has New Recipe and Start Timer in the Mac menu bar

The model writes the call; it shows on Craft's agent map as platform-1, and the files it names are built and tested with the turn.

What a call takes and answers

The answer is a PlatformResult: every file written (path, paths, absolute), a phrase a change (URL scheme recipes, extension SaveRecipeAction (action: url, image)), and a sentence for each assumption and for how the app answers what was added. A call that finds everything already there writes nothing and says so.

The lines

keys:        camera: "takes photos of the dishes you cook"     → INFOPLIST_KEY_NSCameraUsageDescription, iOS and macOS
             faceID: "unlocks your private recipes"           → iOS only
             category: lifestyle                              → public.app-category.lifestyle
             queries: maps, comgooglemaps                     → LSApplicationQueriesSchemes in iOS/Info.plist
commands:    New Recipe ⌘N                                    → File (replaces New Window, which held ⌘N)
             Refresh ⌘R                                       → View
             Kitchen > Start Timer ⇧⌘T                        → a Kitchen menu of the app's own
extensions:  action SaveRecipe "Save to Recipes" accepts url,image
             share ShareToKitchen "Kitchen" accepts text

• A key is a word this agent knows (camera, microphone, photos, photosAdd, localNetwork, location, contacts, calendars, reminders, faceID, bluetooth, speech, motion, tracking, appleEvents, category, displayName, copyright, encryption, fullScreen, queries, bonjour) or an Info.plist key by its own name. A why is made a sentence. A key Xcode has a setting for is written as INFOPLIST_KEY_<key> on the app targets it applies to; a list, or a key with no setting, goes in that platform's Info.plist.
• A command is Menu > Title shortcut, the shortcut as the menu shows it (⇧⌘T) or as typed (cmd+shift+t). With no menu, the title's first word places it (New, Open, Save → File; Show, Hide, Toggle, Refresh → View; Find, Search → Edit; Go, Next, Previous → Go); a title that says nothing of where is refused. ⌘Q, ⌘W, ⌘H, ⌘M, ⌘, and the edit shortcuts are the system's and are refused.
• An extension is action or share, an UpperCamelCase name, the title the share sheet shows (the name's words when left out), and what it accepts: url, image, text (url when left out).
• A line it cannot read, or anything the project cannot take (a menu with no macOS target, an extension with no iOS target), is refused with the reason, every one at once, and nothing is written.

How the project is edited

No model is asked: the same call makes the same files every time, and the same call twice writes nothing. Projects made by granite (objectVersion 77, synchronized folders, a target per platform) take everything; an older project takes keys, schemes, entitlements and the Swift files, with a note naming the files to add to its targets, and is refused an extension.

Testing

swift test                                                  # the record, the schema, the lines, the project text, the calls
PLATFORM_BUILD=1 swift test --filter PlatformBuildTests     # every input on a fixture project, built for macOS and the iOS
                                                            # simulator (Swift 5 and 6), the built Info.plists, entitlements
                                                            # and embedded .appex read, the notifications run

MIT licensed.