First run

The order, and why it is that order

The first question is where your data lives. It is asked before anything else exists, because everything else depends on the answer.

Manifest opens on a provisioning console: a fixed rail on the left carrying the brand, an engraved step track, and a specification readout that fills in as you answer. The right pane holds the active step. On the iPhone the same console runs with the rail turned through ninety degrees into a header, so the two apps ask the same questions in the same shape.

The first screen is Where should your data live?, with two cards side by side: This Mac and Starkive Cloud. Each states its consequence, including the one that costs something. Neither is dressed as the obvious answer, and neither carries a recommended badge.

Continue is disabled until you pick a card. The answer is written to settings before anything else exists, so the workspace is never in a state where it holds data and has no answer to where that data lives.

The demo is a side door, not a third option

It sits below the cards as a link, not beside them as a peer tile.

Under the two deployment cards is a single link: Just looking? Load a demo company instead. Pressing it seeds a complete sample company into its own workspace and drops you into the app. The button reads Loading the demo… while it works.

The demo workspace has setup already stamped, so it never asks you the compliance questions. It also never syncs anywhere. Your real data stays separate, and you can switch between the two from the sidebar.

Choosing a path

Once the deployment question is answered, the second screen offers the two ways forward.

Set up my organization runs the guided wizard: five compliance questions, then a closing step to bring in your first assets. Explore the demo first does the same thing as the link on the previous screen.

The Appearance segmented control below the tiles sets Light, Dark or System. It applies live, so the console re-renders in the chosen look before setup begins. It is here rather than first because light or dark is a preference somebody can change any afternoon, and where a regulated fleet is stored is not.

The five compliance questions

Identity, Organisation, Regulated data, Certifications, Review. The rail on the left fills in as you go, and the answers are read back to you on the last step.

1. Identity

   Two fields: Organisation name and Asset tag prefix. The prefix field carries the help line “Every asset gets a tag like STRK-0001”, using whatever you have typed so far. Continue stays disabled until the name is non-empty.

2. Organisation

   Company size, Industry, Primary jurisdiction, and two toggles: This is a U.S. public company (or a subsidiary of one) and We do business with the U.S. federal government or handle CUI.

   If you pick Other as your industry, a Which frameworks apply to you? grid appears, letting you name the frameworks directly. Industry is a shortcut: four of its values add a framework and the rest add nothing, so somebody whose sector is missing would otherwise be choosing between a wrong neighbour’s rules and no rules at all.

3. Regulated data

   What regulated data do your devices touch? A list of multi-select rows, one per data type. Each one pulls in its governing framework.

4. Certifications

   Certifications you hold or are pursuing. Adopting one includes its evidence set, even without a legal mandate.

5. Review

   The program your answers produced, read back to you. See below.

The rail on the left carries a Specification heading once you have answered anything, and each fact is etched onto it as it arrives: the organisation name, the asset tag sample, the scale, the industry, and on the review step the count of applicable frameworks. On the phone the same facts run across the header instead, anchored to the newest answer.

Reading the review back

The last compliance step is not a summary. It is the one answer you will be asked for in a review, said in the words you will need.

The first panel reads N frameworks · N controls · N evidence reports, with the framework short labels as chips underneath. The second lists each report by title. The third is Your data: followed by the storage location you chose on the first screen.

Below the panels: “You can revisit any of this later in the Compliance Portal.” That is true of everything on this step except the storage location.

Bring in your assets

First run only. Four tiles, and whichever you pick, setup completes and drops you into that flow rather than onto an empty register.

• Import a spreadsheet takes a CSV or Excel export and maps the columns. Best for existing inventories.
• Discover on the network scans your local network to find devices automatically, then asks you to confirm what to add.
• Add one now enters a single device by hand, or scans its serial with your iPhone camera.
• Explore first heads to an empty workspace. You can add assets whenever you are ready.

The footer on this step carries Back, I’ll do this later and the commit button. Choosing any tile stamps setup complete and routes you into the flow you picked.

What setup writes

Two things, and both of them are read by the rest of the app rather than being a record of the wizard.

The asset tag prefix becomes the tag format: mode auto, your prefix, starting at 1. Every asset created afterwards gets a tag in that shape. The compliance answers become the OrgProfile, which drives the Compliance Portal’s applicable frameworks and its one-click Evidence Pack.

Setup is stamped as complete when you press Finish setup or choose an asset tile. Until that stamp exists, the wizard is what the app opens on.

Where to go next

Setup ends with a register, empty or not. The rest of the documentation picks up from there.

• Assets for the register itself: finding a machine, reading its record, and the four ways to add more.
• Retiring a machine for why disposal is per asset rather than a bulk action.