𝑖FLY — the Users & Maker's Guide

What 𝑖FLY is

A daily flight line for one person: the 15-minute time card, the task builder, calendar tasking with chained forecasts and a Kanban flow, folded into one page under the iSight brand. Six views: SIGNAL (today's timeline painted against the declared week, the reserve gauge, locked targets, reminders, the post-flight note), DesigN8 (the kill-chain board), FLIGHT PLAN (month, week, agenda, forecasts), TARGETS (the GTM phases and gates, milestones, weekly indicators), LOGBOOK (time card, mission mix, project accounting, exports, backup), HANGAR (settings, the declared week, versions, data, the Hindsight import, the 𝑖SIP reference files).

The name is the job: find the target, lock it, and remember why. Targets are bogeys; the board is the kill chain; the week you declared on the Mission Card is the plan the timeline is painted against. Ignore the noise.

First flight — five minutes

1. Open the app. It comes seeded with the Block 1 mission mix, the declared week (the Runway phase now, Block 1 from 19 Oct), the ISL-STD-001 project codes, the GTM-001 phases and gates as targets, and the Mission Card dates as reminders.
2. SIGNAL › Fill declared lays the day's declared blocks onto the timeline. Pick a project brush and paint over what actually flew. Note / edit then a block adds a note or points it at a target. Painted the wrong thing? Undo — see below. Every view has a How … works panel at the top — open it once.
3. DesigN8 › sort the BOGEY cards. Lock at most three targets. Put one in FOX. A card's folder on O: comes from its project code; the Folder / file field on the card points deeper when you want it to.
4. HANGAR › check the mission elements, the project codes and the declared week. Change the caps and the reserve thresholds there if you want.
5. LOGBOOK › Backup (.json) once, so you have a copy — it belongs in 40_Products\iFLY\N8_Backups\. Keep doing that weekly (Friday), or in the O: copy link a data file and let Backblaze carry it.

The rhythm it is built for

Morning — the sharp block

Fill declared, confirm the LOCK column, paint the first two hours as you fly them.

During the day

Paint as you go, or use Quick log afterwards. Cards move right as targets fall.

Evening

One line in Post-flight. Overwrite the declared blocks that did not happen.

Sunday 19:00

The reserve gauge is the audit. Green = standing. JOKER = under the target. BINGO = under the floor → shed load or file an A-1, never taken quietly.

Friday

Cadence check (3 LinkedIn · 1 video · 1 newsletter) → TARGETS › Log this week. Then LOGBOOK › Backup, saved to N8_Backups\.

SIGNAL — today's cockpit

Undo. One step back from the last thing that changed your record. It appears three ways: a button inside the little message that pops up the moment something changes, a standing Undo button next to Clear day here and next to Archive debriefed on DesigN8 (rest on it and it names what it will undo), and Ctrl+Z — on a Mac ⌘+Z. While your cursor is in a text box that shortcut belongs to the browser and undoes your typing instead, which is what you want there. It covers moving a card, painting or erasing a stretch of the timeline (the whole stroke goes back in one step, not slot by slot), Fill declared, Clear day, Quick log, editing or clearing a block, and deleting a card — the card comes back whole. Twenty-five steps are kept. Two things it deliberately does not do: survive a reload, and survive a Restore or a Wipe. An undo that came back to life hours later and rewrote days that had since synced from your phone would be a trap rather than a safety net.

The timeline. 15-minute slots (the size is a Hangar setting). The declared window (05:00–20:30 by default) is open; the early and late hours fold above and below it — tap a fold to open it, and anything you paint there keeps it open. Pick a brush — an element, a project code, or a locked target — then tap or drag across slots to paint; Note / edit opens a block; Erase clears one. Fill declared paints the declared blocks into every empty slot; Quick log takes a whole block at once; Clear day asks first.

Setting a time. Wherever a time is asked for — From and To on Note / edit, Quick log and a declared block, the day's start and end in the Hangar, a reminder — the field is 𝑖FLY's own, not the browser's: − and + move it one slot per tap, and tapping the time itself opens a grid of every hour and every quarter so you tap the one you want. Hours outside the declared day are dimmed but still there. Nothing scrolls and nothing keeps moving after your finger lifts, on the phone or the PC. A reminder's grid has an all day chip to clear the time.

Planned versus delivered, on the timeline. A dashed, faint block is a declared block nothing has been painted into yet — the plan, waiting. A solid block is what you flew. The thin coloured strip at the left edge of every slot is what the declared week said that slot was for, so a painted block over a strip of a different colour is a visible deviation. Painted and declared blocks each merge into one labelled run; a run that looks chopped into single slots means the slots differ in project, target or note.

The mission-mix gauges read the week: hours flown against hours declared for each element. The faint tick is declared to date — where you should be by today on the live week (for a past week the tick sits at the full declaration; for a future week it reads through the day showing). The bar turns rust past the declared total. An element with hours flown but nothing declared in the current phase shows a full rust bar and “/ —”; the Mission Card's hr/wk fills in as the denominator only when no declared week exists at all.

The reserve gauge counts uncommitted hours still standing this week: painted reserve on days you have logged, declared reserve on days you have not. Green above the target, JOKER below it, BINGO under the floor.

Locked lists the FOX and LOCK cards. Reminders shows today's, with overdue ones first; the checkbox marks them done. Post-flight is one line for the day. The small W chip beside the date is the day's Hindsight number once you have imported one (see the Hindsight link).

DesigN8 — the kill chain

Eight columns, left to right. On a computer, drag a card with the mouse. On a phone, press and hold a card for a moment until it lifts, then drag it — a quick swipe without the hold just scrolls the board, which is how the two are told apart — or use the ◀ ▶ buttons on the card. The board scrolls on its own, sideways and down, so the column names stay in view however far down a long column you are, and a card can be dropped anywhere in a column's height — it does not have to land on another card. Hold a card near an edge and the board scrolls itself. On a phone the per-column rule text is tucked into How DesigN8 works to leave the cards more room; held sideways, the whole page scrolls so the cards are full size. Each column has a rule and a done-rule.

Sub-tasks and the bar. Open a card and the Sub-tasks section is where you break it into pieces of roughly equal size and tick them off. On the card face you see 2/3 sub-tasks and a thin amber bar — the bar is the sub-tasks, ticked ÷ total, and nothing else. Beside it, 0/6 h logged is a different reading: hours painted against this card on the timeline ÷ its estimate. The two are independent on purpose: the bar says how much of the work you have broken off, the hours say how much time you have flown at it. A card in LOCK or FOX shows its sub-task list on the face itself with tick boxes you can tap without opening the card (Undo works on those too); everywhere else the face shows the count only. The Tasks CSV carries the sub-task text in its last column.

BOGEY

Unidentified contact. Anything that lands on you goes here first — no sorting, no judging.

BANDIT

Identified and prioritized: a project, a due date, an urgency (1 high … 10 low).

TALLY

In sight: broken into sub-tasks of roughly equal size; hours estimated.

LOCK · cap 3

Designated — the only targets that matter this week. The sharp block goes here.

FOX · cap 1

Engaged right now. One at a time; two hours a sitting, then reassess.

HOLDING

Waiting on a person, a part or a decision. Not counted against caps; name the blocker on the card.

SPLASH

Done and, where there is a stakeholder, delivered.

DEBRIEF

Closed out — after the three questions: value vs time · more value for the same effort · faster next time.

A full LOCK or FOX column refuses the next card — Negative, Ghostrider — the pattern is full. A card carries its project, target, urgency, due date, estimate, delay days, sub-tasks, notes and its folder on O: (from the project code by default). Archive debriefed hides closed cards older than two weeks.

FLIGHT PLAN — calendar and forecasts

Month shows, per day: hours logged, cards by due date (solid), cards by forecast date (dashed →), reminders, milestones and gates (◆), and the day's W once Hindsight numbers are in. Click a day to open it in SIGNAL. Week draws the declared blocks faintly and what you flew solidly. Agenda lists the next three weeks.

Forecast dates are ForeTASKing without the macro: every open card's remaining hours (estimate minus hours already painted against it) are poured, in order — FOX first, then LOCK, TALLY, BANDIT; higher urgency first — into the declared capacity of its mission element, one day at a time, skipping days that have none. The date a card's hours run out is its forecast. A fixed date on the card overrides it; delay days push its start. Backlog at declared hours is the same arithmetic in bulk: if it says six weeks and the target is due in two, the caps are doing their job.

TARGETS — the phases, the gates, the week's numbers

What you actually do with targets — four things. First, you do not work from this page; you work from DesigN8. Lock up to three cards there; each card already says which target it serves, so the target moves when the card closes. Second, on Friday, five minutes: press Log this week in LEADING INDICATORS and type the numbers, then open LOGBOOK › roll-up and type the 50.* share (the part of your 𝑖Sight hours that went to distribution codes) into the Build freeze target. Third, when a target's measure is met — the number in its "measure" line — open it and set its status to done; targets with linked cards score themselves as the cards close, so most of the time there is nothing to type. Fourth, on a gate's date, read the number and follow the rule written in the gate. That is all this page asks of you. Everything else on it is the scoreboard: THE PLAN at the top right holds the six sentences the whole thing serves, with a button that opens the filed plan.

The war by year. A phase is a time box with a name (Runway sprint, Publish, Teach); a target is one outcome that must be true by a date, with a measure — the number that says it is done; a gate is a pre-committed check with a date and a rule for what happens on a miss; a milestone is a date that matters. The seed carries the ISL-PLN-002 campaign (four phases, three gates), the Block 1 dates from the Mission Card, and two more theatres — Airframe · Block 1 for the person and Shop · business ops for the admin — so the campaign's numbers are not diluted by errands.

Progress scores itself. A target with cards linked to it (the Serves target field on a card) reads its progress from those cards — closed cards over all cards; a phase averages its targets; a target with nothing linked uses the percentage you type. The big number at the top averages the year.

Weekly indicators — subscribers, assessment completions, captures, LinkedIn posts, videos, lab notes, L1 sales, inbound inquiries, artifacts shared, paying members and cohort applications — are logged once a week with Log this week, so the Friday cadence check has a place to land. The cadence they are scored against is set in the Hangar (Rev B: 2 LinkedIn · 1 video · 1 lab note a week).

When the contract opens, the milestone and the reminder named USAF contract opens move to the same day as the declared week's phase change in the Hangar.

How TARGETS, DesigN8 and the HANGAR fit together

Three questions about any hour you fly, and each view answers one of them.

WHY — TARGETS

A target is what the work is for: an outcome, a date, and the number that proves it. A target is never the work itself. The test: if you could finish it in an afternoon, it is a card, not a target. "Cohort 1 fills — 8 seats by 15 March" is a target. "Write the cohort landing page" is a card.

WHAT — DesigN8

A card is one sortie: a piece of work you can finish, with a project code, an estimate, a due date, and a Serves target. It walks BOGEY → BANDIT → TALLY → LOCK → FOX → SPLASH → DEBRIEF. The link to its target is what makes the target score itself; a card with no target is a chore, and that is allowed — it just moves nothing on the war map.

WHERE — HANGAR

A project is a place, not a purpose: an ISL-STD-001 code and folder (40.SITE, 50.PUB) where the hours are accounted in the Logbook. Mission elements are the rows of the Mission Card. The declared week is the schedule the timeline is painted against. Nothing in the Hangar says why an hour was flown; it says where it landed.

The hour itself. On SIGNAL you paint a slot with a brush. An element brush says only which mission element it was (family, ground, reserve). A project brush also says where the hour is accounted. A card brush — only cards in LOCK or FOX appear as brushes — also says which target it moved. When you are working a locked card, paint with the card brush: then the Logbook, the card's hours-against-estimate, the forecast dates and the target's progress all read from the same slot, and nothing has to be entered twice.

The chain, in one line. Hangar project (where) → DesigN8 card (what, this week) → Target (why, by when) → Indicator (the number that says the campaign is working). Plan from the right end: pick the target, write the measure, then cut the cards that would move it, then lock at most three.

Rule of thumb: the Hangar holds nouns, DesigN8 holds verbs, TARGETS holds results. If a "target" has no measure and no date, it is probably a card. If a card would take months, it is probably a target that still needs cutting into cards.

LOGBOOK — the accounting

Time card — hours by code × day for the period you pick (week, month, custom). Mission mix compares declared and flown for the period. Roll-up follows ISL-STD-001: by zone (Business 00–20 · Work 30–50 · Stores 60–90) and by folder number. Project accounting shows budget, logged, remaining, burn and value at rate for any project with a budget or a rate set in the Hangar. Return in W (under the time card) is the Hindsight cross-read — which work pays, in your own numbers.

Exports — Time log · all (CSV) (12 columns: Date, Weekday, Start, End, Hours, MissionElement, ProjectCode, Project, Folder, Zone, Task, Note) for the Excel companion; Projects (CSV); Calendar (.ics) for reminders (in the claude.ai copy it saves as .ics.txt — rename it before importing).

Backup (.json) writes the whole dataset to a file. Merge in (.json) folds a backup into this copy — card by card and day by day, the newer edit wins, nothing already here is dropped; it is the way to bring a local-only copy's days across. Restore replaces everything in this copy with the file, and in a synced copy that becomes the shared dataset — it warns first; use it for a rollback, not for bringing data across. Both take a snapshot before they touch anything.

The nine folders. A project code is NN.NAME; the number is the top-level folder on O: under ISL-STD-001, and the roll-up sums hours by it. 00_Admin entity, SAM, insurance, licenses, subscriptions · 10_Money banking, Stripe, Wave, tax · 20_Contracts SOWs, subcontracts, proposals, NDAs, invoices out · 30_Engineering client ASIP work · 40_Products Site, Daily, MmM, iSIP, iSRM, iFLY · 50_Market brand, social, YouTube, podcast, KDP · 60_Library research, reading, NIMH, PhD · 70_Media raw video and audio masters · 90_Archive dissolved, superseded, kept for the record. The roll-up lists all nine even when a folder has no hours yet, so the empty ones are as visible as the busy ones; the same legend sits under Hangar › PROJECTS, and resting on any code names its folder.

HANGAR — settings, the declared week, data

Mission elements are the rows on the Mission Card; their hr/wk is the declared number. Projects carry the ISL-STD-001 code, folder, customer, budget and rate. The declared week is what paints the timeline: a phase has dates and one block list per weekday, and the phase whose dates contain a day supplies that day's blocks. When the contract opens: set the Runway phase's end date to the day before, and Block 1's start to the first day — the timeline, gauges and forecasts follow.

The day & the week — slot size, the declared window, week start, waking hours, the reserve target / JOKER / BINGO thresholds, the LOCK and FOX caps, and whether the W shows on the Flight Plan calendar. Versions — the changelog, and Data history: a snapshot is taken the first time the app opens each day (30 kept) and before every restore, merge, reset or wipe; restore, pin, download or delete any of them. Snapshots live in the browser they were taken in.

Data — Backup, Merge in, Restore, Reset to the Block 1 seed, Wipe everything (all ask first, in the app's own dialog), the Hindsight Daily import, and a Sync check line with counts for when something looks off. 𝑖SIP Reference — see below; since v1.9 it has a fourth slot, The plan, for the ISL-PLN-002 reader copy or PDF, which TARGETS › Open the plan shows inside the app. If a phone answers Could not file it, the Storage check line under the panel says the real reason; text files fall back to the browser's local storage, PDFs cannot — file the HTML reader copy there.

Anything destructive asks first in the app's own dialog: deleting a target, a card, a project, an element, a phase or a snapshot; Clear day; Restore in a synced copy; Reset; Wipe. Escape or Keep backs out; Enter or the amber / rust button goes ahead.

The Hindsight Daily link — W in the cockpit

Hindsight 80/20 Daily is the instrument that measures the day: one number, W, 0–10, every night. 𝑖FLY can carry that number so the two logbooks line up. The route is two steps:

1. In Hindsight Daily: Data › Export backup file (or Share on the phone). It saves hindsight8020_backup_YYYYMMDD.json.
2. In 𝑖FLY: Hangar › Data › Import Hindsight backup (.json) and pick that file.

𝑖FLY keeps only the numbers — one W per day, rounded to two places — and nothing else. The notes never enter 𝑖FLY: not its storage, not a backup, not the cloud store. Importing again replaces the set; Remove Hindsight data takes it out. The numbers save, back up, snapshot and sync like the rest, so one import on the PC reaches the phone. They show as the W chip on SIGNAL (green at 7 and above, cream from 5, rust below; W — means not logged yet — tap it to open the Daily), as a faint W 8.5 in the Flight Plan cells, and in Return in W on the Logbook: for every painted day in the period that also has a W, the project code holding at least 40 % of the painted hours led the day; the fold shows days led, hours, the mean W on those days (once a code has led three) and Δ against the period's overall mean, by code and by element. Association only, in your own record — the Daily measures the day; 𝑖FLY only lines the two logbooks up.

𝑖SIP Reference

Hangar › 𝑖SIP Reference keeps the filled Companion Workbook, the Mission Card and the Mission Declaration one tap away, the way the Daily does. Upload files a PDF, HTML, Markdown or text copy (up to 24 MB) into one of the three slots; Open shows it inside the app (Escape or Close comes back); Replace and Remove do what they say. These files live in the browser you filed them in — not in the JSON backup, not in the cloud store — so file them again after a device change. In the claude.ai copy a PDF is drawn by a viewer library fetched on demand the first time; Download there is best effort, and the original in the workbook folder is the copy to open.

The phone — the route that works

1. Install the icon once. Open isightlabs.netlify.app/ifly/ in Safari and tap Install the Home Screen icon. Safari asks to allow a configuration profile — Allow. Then Settings › General › VPN & Device Management › 𝑖FLY (Safari) › Install. It says Not Signed; it is ours, and it adds one icon and nothing else.
2. Tap the icon. Safari opens straight into 𝑖FLY, signed in as you are in Safari, the chip reading cloud sync on. The first time, claude.ai shows a white "Claude by Anthropic — Open in the Claude app" strip with no close button.
3. Tap OPEN once. The link bounces through the Claude app and comes back without that strip. If it ever behaves differently, scroll the white area above the app upward — the strip is part of the page.
4. Hide Safari's toolbar. Page-menu icon at the left of the address bar › Hide Toolbar. Only a small claude.ai pill remains; tap it to get the bars back.
5. Paint. A tap paints one slot; tick drag on touch to drag across slots. Portrait suits the timeline; landscape suits DesigN8 and the Logbook tables.

What does not work, so nobody tries it twice: Add to Home Screen from Safari (claude.ai's own web-app settings send that icon to the Claude home page); the full-screen profile (opens full screen, but iOS does not pass taps to the timeline inside it — reading only); a Netlify-hosted copy of the app (it would lose the phone↔PC sync and put the task list on a public site).

If the page ever looks wider than the screen and slides sideways as you edit, that is Safari's zoom-on-focus: it enlarges the page when a field's text is under 16px and leaves it that way. v1.7.1 sizes every field at 16px on iOS so it no longer triggers; if a zoomed page is still on screen, pinch it back or close the tab and open the icon again. The other cause was a filed reference PDF with a long name that could not wrap (fixed in v1.7.2 and finished in v1.7.3) — the tell is extra background to the right of the panels, or a filename running past its panel.

iOS puts a tab to sleep when you leave it. The app re-pulls the shared dataset every time it comes back into view, re-opens a live link that died, and retries a cloud write that failed until it lands — the chip's time is the last successful sync. If a deleted card seems to linger, scroll a little or tap another tab and come back.

Where the data lives, and sync

Opened from the claude.ai link, every device shares one dataset through a private store that belongs to the artifact: edit a card on the phone and the PC has it within seconds. Merges are item by item — the newer edit of each card, target, reminder or day wins, and a deletion is remembered so an older copy cannot bring the item back — so working on both in the same hour is safe. The file on O: saves to that PC's browser and, if you link one, to a data file in your tree; no cloud.

If the phone does not show what you did on the PC yesterday, it is one of three things, in this order of likelihood. One: the PC work was done in the file copy on O: — the one whose folder is named NOTsynced — which never leaves that browser; the chip beside the clock reads local only · not synced in that copy. Two: the PC tab was closed within a second or two of the last edit. An edit reaches the cloud about a second and a half after you stop; before v1.13 an edit caught inside that window stayed on the PC until the next time that same copy was opened. Since v1.13 the page flushes the moment it is hidden, so this one should be gone. Three: both devices edited the same day, and the phone edited it later — days merge as whole days, newest wins, so the phone's version of that day replaced the PC's. Opening 𝑖FLY in Safari or through the Claude app makes no difference: the home-screen icon, the site's launcher and the Claude app all open the same claude.ai link and share one store. To check what a copy last did with the cloud: Hangar › Data › the Sync check line.

Recommended: the claude.ai link as the daily driver on both PC and phone; back up to O: weekly (Logbook › Backup → N8_Backups\). Nothing in either copy is visible to anyone but you.

If your work seems to have vanished

Painted time is not gone unless the browser it lived in threw it away. The drill:

1. Go back to the exact place you were painting — same device, same browser, same way of opening it. Data is stored by that browser, per place.
2. If the days are there and the chip says cloud sync on, you are done — the app pushes them on open and the other devices pick them up.
3. If the days are there but the chip says local only: LOGBOOK › Backup (.json), then open the claude.ai link and LOGBOOK › Merge in (.json) with that file.
4. If the days are not there: HANGAR › Data history. Restore the newest snapshot that shows the right number of logged days.
5. A file-card preview inside a chat is the one place that may not keep data at all. If that is where the painting happened and nothing is in Data history there, the time has to be re-entered — SIGNAL › Quick log takes a whole block at once.

The Excel companion

LOGBOOK › DATA › Time log · all (CSV) → open the CSV → copy rows 2 down → paste as values into the companion's TimeLog sheet at A2 (delete the example rows first). TimeCard takes a month in B1; MissionMix takes a Monday in B1. Projects (CSV) pastes into Pkey the same way. The companion is iFLY_Companion_v1.0.xlsx beside the offline copy; if the CSV columns ever change, it must follow.

The drawer — keeping it under ISL-STD-001

The drawer is THE_WORK\40_Products\iFLY\: the offline copy and the Excel companion in iFLY_LocalPCcopy_NOTsynced\, backups in N8_Backups\, superseded builds in Old\, the sources zip, icon assets and build report in Build_Info\, this guide as iFLY_Guide.html, the README and the handoff beside it, and a copy of the Netlify drop folder. The live launcher, install page and this guide deploy from 40_Products\Site\Ship_NETLIFY\ifly\. New builds replace iFLY.html in the local-copy folder; the one they replace goes to Old\ with its version in the name. Files on O: are never deleted.

Maker's notes — changing the app

Sources. The app is seven parts concatenated by build.py: 01_head.html (CSS and head), 02_body.html (header, tabs, the six views, dialogs, this guide's overlay), 03_core.js (constants, changelog, persistence, slots, phases, gauges, forecasts, reminders, exports, cloud sync, snapshots, import/merge, the Hindsight and reference modules), 04_seed.js (the seed state), 05_views1.js (SIGNAL, the board, editors, help panels, the ask() dialog), 06_views2.js (PLAN, TARGETS, LOGBOOK, HANGAR, init), 07_guide.html (this guide). They live in Build_Info\iFLY_src_v1.x.zip.

The cycle. Unzip → edit → python3 build.py (writes iFLY.html, iFLY_artifact.html, iFLY_Guide.html) → node --check /tmp/ifly_all.js → run the tests (smoke.py, verify10, verify13, verify14, verify15, sandbox_repro.py) → bump APP_VERSION and add a CHANGELOG line in 03_core.js → publish iFLY_artifact.html to the existing artifact URL (capabilities carry forward; never pass a favicon) → move the previous iFLY.html to Old\iFLY_v1.x.html and drop the new one in the local-copy folder → zip the sources → update the README, this guide and the handoff if behaviour changed.

Rules that were paid for. Never call confirm(), prompt() or alert() — the claude.ai frame swallows them; ask through ask(). Never loosen the sync rules: seed cards keep fixed ids, a fresh copy adopts the cloud instead of seeding over it, merges are item by item with tombstones, Restore replaces and Merge in folds, everything from a snapshot is cloned before it enters state. S.hs merges as one object, newer imported wins, and a removal writes a dated empty object so it wins everywhere. Reference files stay in IndexedDB ifly-ref, never in a backup or the cloud. Keep the app off public hosting — the seed embeds the task list and sync exists only inside claude.ai. Never mobile-collapse a vertical day grid into a horizontal strip.

Where things are. The artifact URL is in the handoff and in the README; the launcher and install page are in Site\Ship_NETLIFY\ifly\ (with _headers at the Ship root for the .mobileconfig MIME type); brand assets in 50_Market\Brand\; the decision history in Claude's memory and iFLY_HANDOFF.md. Start a new build chat with the handoff's starter prompt and the current sources zip.

Plain words — the terms this app and the plan use

Target

An outcome that must be true by a date, with a measure — the number that says it is done. "Cohort 1 fills — 8 seats by 15 March." Never the work itself.

Card (a sortie)

One finishable piece of work on DesigN8: a project code, an hour estimate, a due date and the target it serves. "Write the cohort landing page."

Phase

A time box that groups targets — Runway sprint, Publish, Teach, Prove & decide. Its progress is the average of its targets.

Gate

A pre-committed check on a date, with the rule written in advance: "300 subscribers by 31 January; under 150, stop and rewrite." It keeps a wrong guess from costing a year.

Milestone

A date that matters but is not work: the contract opening, recertification.

Theatre

One of the three groups of targets: the Campaign (selling), the Airframe (you), the Shop (business admin). Each is a phase so their scores stay separate.

Indicator

A weekly number the plan is scored on — subscribers, cadence, sales, members, applications. Logged on Fridays. Revenue comes months after these move.

Cadence

The publishing rhythm you promised yourself, per week — set in the Hangar (Rev B: 2 LinkedIn cuts, 1 short video, 1 lab note).

Lab note

The weekly email — one instrument, one finding, one idea, written from your own record. The LinkedIn cuts and the short video are cut from it.

Beachhead

The one audience you land with first. Rev B: the channel is engineers inside institutions (where you publish); the person is the one in that room who took the left turn for a family.

Front door

The one free thing a visitor is asked to do — take the Mind My Material assessment. Everything else on the site is the catalogue behind it (the Hangar page).

Capture · nurture

Capture = the email field at the end of a free tool. Nurture = the short series of emails that follows (five in Rev B), so a new name does not go cold.

Cohort

A small group taught live over six weeks — Rev B's first paid offer. "Founding price" = the lower first-run price ($500) that pays for the testimonials.

Membership

The Patreon tiers ($7 Observer, $25 Analyst) — the container the cohort's alumni land in, not the engine.

Mission element

A row of the Mission Card — family, ground, reserve, 𝑖Sight, body, social, contract — with its declared hours a week. The gauges read these.

Declared week

The schedule you said you would fly: one block list per weekday, per phase (Runway → Block 1). The timeline is painted against it.

Reserve · JOKER · BINGO

Reserve = uncommitted hours still standing this week (target 16.25). JOKER = under the target. BINGO = under 10 — shed load or file an A-1 (a formal exceedance).

Brush

What a painted slot is tagged with: an element (what kind of hour), a project (where it is accounted) or a locked card (which target it moved).

Roll-up

Hours added up by folder number and zone (Business 00–20 · Work 30–50 · Stores 60–90). The 50.* share is the distribution share.

Merge in · Restore · Snapshot

Merge in folds a backup into this copy, newer edits winning on both sides. Restore replaces everything with the file. A snapshot is the automatic copy taken before either, and daily.

Tombstone

A note that says "this item was deleted on this date", so a deletion wins over an older copy on another device instead of coming back.

Versions

iSight Laboratories LLC · isightlabs.netlify.app · Questions: isightlaboratories@gmail.com