Intelgic delivery dashboard

Week 2026-W38 · generated 2026-09-16T19:08:42+00:00 ·

Contents

You are on Weekly track

What the flags are i

You are on Hours

This weekOverall

Other tabs

Other pages

Right now

The four questions that get asked every day, on one screen, as of 2026-09-16: what is moving, what is due, what is moving with no date on it, and what is stuck behind something else.

Moving

36
in progress or in test

Due ahead

9
dated commitments still in the future

Dates already passed

22
open work whose due date has gone by

No date at all

16
being worked on, nothing promised

What is due next

Only 9 pieces of open work anywhere on the board carry a due date in the future. That is the honest state of the schedule: the board is not tracking dates, so this list is what has been promised a date rather than everything that is coming.

TicketWhat it isStageWhoDue
INTEL-292Single Sign-On (SSO) for Certainty ClientIn ProgressNirupam Jana2026-09-16 in 0d
INTEL-287Fanuc robot world environment setupIn Progressroddur.g2026-09-17 in 1d
INTEL-289Hardware Setup for testing environment (Rhitban & Madhusudan)In Progressrajesh.m2026-09-17 in 1d
INTEL-511Multi Camera Imaging ScreenTo DoSriparna Biswas2026-09-18 in 2d
INTEL-822Procure Cat8 Cable (50m) for Three Line Scan CamerasTo Dorajesh.m2026-09-18 in 2d
INTEL-837Inventory Report Template DesignIn Progressabhisek.k2026-09-18 in 2d
INTEL-503Role-Based Permission Backend on Server SideIn Progresspabitra.d2026-09-21 in 5d
INTEL-293Role-Based User Management in Certainty ClientTo Dopabitra.d2026-09-25 in 9d
INTEL-295SOP Monitoring: Multi-Camera, Multi-Model, Rule Engine, Multi-Feed RuntimeIn ProgressBiplab Bag2026-09-25 in 9d

Dates that have already gone by

Still open, with a due date in the past. Most need either a new date or a decision that the date never meant anything — carrying 22 silently overdue items is how a board stops being believed.

TicketWhat it isStageWhoDue
INTEL-269Client ManagementPush to DevNirupam Jana2026-08-28 19d late
INTEL-66[BiplabB-Intelgic] SOP - Dynamic work instruction setup and Runtime Inspection - AI AgenPush to DevBiplab Bag2026-09-03 13d late
INTEL-244Activity LogPush to Devpabitra.d2026-09-03 13d late
INTEL-248Send the client list (company to contact) and the POC mappingTo DoIntelgic2026-09-04 12d late
INTEL-249Send the Bobrick SOP monitoring document (UI and workflow)In ProgressBiplab Bag2026-09-04 12d late
INTEL-250Comment on and move the cards for the licence PRs in both repositoriesTo DoSriparna Biswas2026-09-04 12d late
INTEL-254Send the current email addresses for Madhusudan and Abhishek cloud accessTo Donobody2026-09-04 12d late
INTEL-259Hardware ManagementPush to Devpabitra.d2026-09-04 12d late
INTEL-260Creating a user with a soft-deleted username returns 500Push to DevKunal Dutta2026-09-04 12d late
INTEL-262installer/ is gitignored — Windows and Linux installer sources are untrackedPush to DevKunal Dutta2026-09-04 12d late
INTEL-252Install the SSL certificate on the Stakes deploymentTo Dorajesh.m2026-09-05 11d late
INTEL-284Release builds ship chat/ and voice/ Python as source instead of .pycPush to DevKunal Dutta2026-09-08 8d late

Showing 12 of 22. The rest are in Segments.

Blocked, and what it is holding up

Four tickets, all on the QA and infrastructure side. The last column is the one that decides priority: what stops if this stays stuck.

TicketWhat it isWaiting on Holding upWho
INTEL-15 QA-E6: Draft HIL (hardware-in-the-loop) bench requirements outline (with Rajesh/
HIL bench requirements cannot be drafted without their input; the summary says so explicitly.
Rajesh and Jhantu INTEL-32
The hardware test bench. Nothing can be tested against real industrial hardware until the requirements exist, and INTEL-32 cannot start procurement without them.
erikdon.p
INTEL-30 AWS access monitoring + pipeline-failure alerting setup (ties to Rajesh's explic
AWS access monitoring and pipeline alerting is scoped as Rajesh's explicit ask and sits behind the INF-E3 infrastructure work.
INF-E3 / Rajesh no other ticket waits on it
Knowing when a pipeline or an AWS access problem happens, rather than finding out from a customer.
erikdon.p
INTEL-31 INF-E4: CI/CD pipeline monitoring dashboards + alert tuning
Pipeline monitoring dashboards tune alerts on a pipeline that INTEL-34 is still finalising against real repos.
INTEL-34 (and INTEL-147, now Done) no other ticket waits on it
Alerting on the build pipeline. Lower stakes than the others: it tunes a pipeline that is itself still being finished.
erikdon.p
INTEL-32 QA-E6: HIL bench procurement research (vendor/spec options)
Procurement research needs the bench requirements INTEL-15 has not produced yet.
INTEL-15 no other ticket waits on it
Buying the bench. Procurement lead time sits behind this, so every week it waits is a week added to the far end of QA readiness.
erikdon.p

Working on something with no delivery date

Not late, and not wrong — but nothing on the board says when any of it lands, so none of it can be counted on in a plan.

PersonItems Tickets
Kunal Dutta6INTEL-177 INTEL-236 INTEL-59 INTEL-68 INTEL-69 INTEL-73
Nirupam Jana5INTEL-107 INTEL-108 INTEL-110 INTEL-314 INTEL-865
nobody1INTEL-282
Derek1INTEL-8
Erven.j1INTEL-141
Sriparna Biswas1INTEL-71
taylor1INTEL-23

Completion

Week of 2026-09-14. 154 of 635 pieces of work are finished. Counted in stories, tasks and bugs — the sub-tasks underneath them are left out, so a team that breaks its work down finely is not flattered.

finished: To do 445, In progress 7, In QA 29, Done 154To do: 445In progress: 7In QA: 29Done: 15424%finished
StageItemsShare
To do44570%
In progress71%
In QA295%
Blocked00%
Done15424%
Total counted635100%

29 items are past development and sitting in test or waiting on a deployment.

How these five stages map onto the nine statuses this board uses
  • To doTo Do, Backlog
  • In progressIn Progress
  • In QATesting, QA, Push to Dev
  • Blocked — not a status on this board, see below
  • DoneDone, QA-pass

4 issues are Removed or Rejected. They are excluded from the total above rather than counted as finished or outstanding, so the percentage describes live work only.

Blocked is not a status here. This board has no Blocked status, and the collected fields carry no issue links or description text, so nothing here is machine-derived. These are open tickets whose own summary names a person or ticket they wait on, read by hand on 2026-09-14. Treat it as a floor, not a count: a ticket blocked for a reason nobody wrote down does not appear.

Statuses that fit no stage and are therefore not in the chart: Blocked (4).

Each area on its own

The same five stages per group of work. The percentage in the middle of each ring is how much of that group is finished.

Certainty product

: To do 37, In progress 1, In QA 18, Done 84To do: 37In progress: 1In QA: 18Done: 8460%

84 of 140 finished · 18 in QA · 0 blocked

Customer deployments

: To do 74, In QA 1, Done 7To do: 74In QA: 1Done: 79%

7 of 82 finished · 1 in QA · 0 blocked

POC

: To do 1To do: 10%

0 of 1 finished · 0 in QA · 0 blocked

Internal & ops

: Done 1Done: 1100%

1 of 1 finished · 0 in QA · 0 blocked

Unsegmented

: To do 333, In progress 6, In QA 10, Done 62To do: 333In progress: 6In QA: 10Done: 6215%

62 of 411 finished · 10 in QA · 0 blocked

What “blocked” means here

Every ticket counted in the red slice, with what it is waiting on and where that was read from. Four tickets, all of them Erik’s or Rajesh’s side of the QA and infrastructure work.

Since this snapshot was taken, the board has gained a Blocked status, a flag on each of these four tickets and an is blocked by link where the thing they wait on is itself a ticket. From next week’s collection this slice is read from the board rather than compiled by hand, and it will count anything the team marks — not only the four somebody happened to write down.

TicketWhat it isWaiting onAssigneeRead from
INTEL-15QA-E6: Draft HIL (hardware-in-the-loop) bench requirements outline (with Rajesh/Jhantu input)
HIL bench requirements cannot be drafted without their input; the summary says so explicitly.
Rajesh and Jhantuerikdon.pINTEL-15 summary, W37 cache
INTEL-30AWS access monitoring + pipeline-failure alerting setup (ties to Rajesh's explicit ask)
AWS access monitoring and pipeline alerting is scoped as Rajesh's explicit ask and sits behind the INF-E3 infrastructure work.
INF-E3 / Rajesherikdon.pINTEL-30 summary, W37 cache; INF-E3 epic naming
INTEL-31INF-E4: CI/CD pipeline monitoring dashboards + alert tuning
Pipeline monitoring dashboards tune alerts on a pipeline that INTEL-34 is still finalising against real repos.
INTEL-34 (and INTEL-147, now Done)erikdon.pINTEL-31 and INTEL-34 summaries, W37 cache
INTEL-32QA-E6: HIL bench procurement research (vendor/spec options)
Procurement research needs the bench requirements INTEL-15 has not produced yet.
INTEL-15erikdon.pINTEL-32 and INTEL-15 summaries, W37 cache

The headline numbers

The measures the automated checks produce, with their coverage printed inside the cell where a figure covers only part of the board.

MeasureValue
Open issues with no status change in 14d 117
Open issues with no assignee 293
Overdue open issues i26 (99 of 865 — 11.4% have a due date)
Open issues with no epic 363
Days showing a bulk-edit fingerprint i14
Same, by the `updated` field (MISLEADING — shown for contrast) 77
PRs merged with no review 25
Branch pairs with an unpromoted gap 6

Everyone with work on the board

All 17 assignees, not only the four people the reassignment view covers. This chart counts every issue including sub-tasks, so the totals here are larger than the 635 above — a person holding ten sub-tasks of one story appears as ten items.

(nobody assigned): To do 290, In QA 1, Done 32; taylor: To do 180, In progress 1, Done 20; Derek: To do 93, In progress 1, Done 8; Kunal Dutta: To do 13, In QA 14, Done 23; erikdon.p: To do 4, Done 18; Erven.j: To do 7, In QA 1, Done 17; Nirupam Jana: To do 3, In progress 2, In QA 8, Done 9; Sriparna Biswas: To do 6, In progress 1, In QA 4, Done 10; pabitra.d: To do 3, In progress 1, In QA 2, Done 12; rajesh.m: To do 7, In progress 1, Done 5; jhantu.d: To do 3, In progress 2, Done 6; Intelgic: To do 10; Biplab Bag: To do 1, In progress 2, In QA 1, Done 6; roddur.g: To do 6, In progress 1, Done 2; Rhitban Sarkar: To do 2, In progress 4, Done 3; Madhusudan Mandal: To do 4, In progress 1, Done 1; abhisek.k: In progress 1, In QA 3, Done 1(nobody assigned)To do: 290290In QA: 1Done: 3232323taylorTo do: 180180In progress: 1Done: 2020201DerekTo do: 9393In progress: 1Done: 88102Kunal DuttaTo do: 1313In QA: 1414Done: 232350erikdon.pTo do: 44Done: 181822Erven.jTo do: 77In QA: 1Done: 171725Nirupam JanaTo do: 33In progress: 22In QA: 88Done: 9922Sriparna BiswasTo do: 66In progress: 1In QA: 44Done: 101021pabitra.dTo do: 33In progress: 11In QA: 22Done: 121218rajesh.mTo do: 77In progress: 11Done: 5513jhantu.dTo do: 33In progress: 22Done: 6611IntelgicTo do: 101010Biplab BagTo do: 11In progress: 22In QA: 11Done: 6610roddur.gTo do: 66In progress: 11Done: 229Rhitban SarkarTo do: 22In progress: 44Done: 339Madhusudan MandalTo do: 44In progress: 11Done: 116abhisek.kIn progress: 11In QA: 33Done: 115To doIn progressIn QABlockedDone

The largest row is nobody. 291 open items carry no assignee at all — more than every named person put together. Most of it is one customer backlog, Polyplex, whose 150 open items nobody has divided up: a planning gap rather than sixteen people ignoring work.

PersonItems Where they are
(nobody assigned)323291 open of 323 — 1 past code and in test or deployment. Mostly: Polyplex (155); Unsegmented (29).
taylor201181 open of 201 — 1 in progress. Mostly: Under an epic not in the lane map (179); No epic anywhere up the parent chain (2).
Derek10294 open of 102 — 1 in progress. Mostly: Under an epic not in the lane map (92); Certainty Client (2).
Kunal Dutta5027 open of 50 — 14 past code and in test or deployment. Mostly: No epic anywhere up the parent chain (14); Certainty Core (9).
erikdon.p224 open of 22 — nothing started. Mostly: Under an epic not in the lane map (6); Certainty Core (2).
Erven.j258 open of 25 — 1 past code and in test or deployment. Mostly: Certainty Core (3); Under an epic not in the lane map (2).
Nirupam Jana2213 open of 22 — 8 past code and in test or deployment, 2 in progress. Mostly: Certainty Client (4); SSO for Certainty Client (4).
Sriparna Biswas2111 open of 21 — 4 past code and in test or deployment, 1 in progress. Mostly: Polyplex (8); No epic anywhere up the parent chain (3).
pabitra.d186 open of 18 — 2 past code and in test or deployment, 1 in progress. Mostly: Certainty Core (4); Unsegmented (1).
rajesh.m138 open of 13 — 1 in progress. Mostly: No epic anywhere up the parent chain (6); Polyplex (2).
jhantu.d115 open of 11 — 2 in progress. Mostly: Polyplex (4); No epic anywhere up the parent chain (1).
Intelgic1010 open of 10 — nothing started. Mostly: No epic anywhere up the parent chain (10).
Biplab Bag104 open of 10 — 1 past code and in test or deployment, 2 in progress. Mostly: Unsegmented (2); Certainty Core (1).
roddur.g97 open of 9 — 1 in progress. Mostly: No epic anywhere up the parent chain (6); Unsegmented (1).
Rhitban Sarkar96 open of 9 — 4 in progress. Mostly: Polyplex (5); No epic anywhere up the parent chain (1).
Madhusudan Mandal65 open of 6 — 1 in progress. Mostly: IntelgicPOC (3); Stakes MFG (1).
abhisek.k54 open of 5 — 3 past code and in test or deployment, 1 in progress. Mostly: Reliant Cellular (3); No epic anywhere up the parent chain (1).

The platform, coloured by where the work has got to

Every piece of Certainty, read top-down: the platform itself first, because that is the part that works today, then the people who use it, then the cloud being built now, and last the fleet view nobody has bought. Hover any box for what it is, where that definition came from, and the tickets behind its colour.

The platform

Not startedIn progressBlockedIn testDone on the boardNot on the board

A percentage under a box comes from that box's own tickets. A milestone code instead — M4 · 0 of 27 done — means no developer ticket sits under that box's epic, so what is quoted is the scope of the milestone that builds it. Those counts belong to the milestone, which usually builds more than one box, so they cannot be added up across the diagram. Hover for the milestone name and a link straight to its cards.

runs inspectionsruns inspectionsasks: is this a defectasks: is this a defectrecords resultsrecords resultssends results outclaims its licenceissues licencesissues licenceskeeps customers apartkeeps customers aparthistory per customerhealth and faultshealth and faultssends updates inmany sites at oncemany sites at oncewhat is allowed out The platform - works todayPeopleBeing built nowAlso neededLater - many plants at once
Certainty Core49% done

Certainty Core In test

The inspection engine that sits in the factory. It talks to the cameras, the lasers and the machines on the line, runs the inspection, and decides pass or fail.

The single most complete thing on the board, and the reason a demo can be given at all.

Where this definition comes from: Derived from its 49 tickets — OPC UA, SCADA, 3D profilers, the defect-detection pipeline — and matches the architecture review's description of a .NET service on the plant machine.

Code: Code exists — Found in the repositories by the architecture review.

Epics: INTEL-38

In the plan: M3 · Tenant and entitlement — 0 of 20 done, 72h, which also builds Entitlement service, Multi-tenant setup; M4 · Remote monitoring and fault reporting — 0 of 27 done, 97h, which also builds Observability; M2 · Transport security, key escrow and the recipe boundary — 0 of 30 done, 126h, which also builds Certainty Client, Key escrow. open the 77 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

  • INTEL-104 [kunald-intelgic] Activity LogDone
  • INTEL-143 Vision pipeline exec()s Python named by a recipe, and the comment callTo Do
  • INTEL-144 Seventeen unbound names in authored Python -- NameError at runtime in Done
  • INTEL-145 flutter_web/ is 40MB of committed build output and the application bunDone
  • INTEL-147 No CI -- fourth repository, fourth time, and this one has the most to Done
  • INTEL-148 Restore is not reproducible -- no SDK pin, no lockfile, and four declaDone
  • INTEL-149 174 build warnings, including 132 platform-compatibility warnings agaiTo Do
  • INTEL-150 Losing sqlite-key.enc makes the encrypted database permanently unreadaDone
  • INTEL-151 No Python lint configuration exists, so there is no agreed standard toTo Do
  • INTEL-152 Only a dev branch exists -- the three-branch model has not reached thiDone
  • INTEL-153 About 152MB of vendor SDK binaries committed to gitTo Do
  • INTEL-154 Swagger unauthenticated when enabled, BOM breaks .gitattributes, orphaTo Do
  • INTEL-244 Activity LogPush to Dev
  • INTEL-259 Hardware ManagementPush to Dev
  • and 35 more
Vision + AIM7 · 0 of 19 done

The vision and AI stack Not on the board

The part that actually looks at the picture: the models that spot a defect, read a label, or measure a part. It runs on the plant machine, not in the cloud.

No epic covers it. It is built, and invisible on the board — so a chart of tickets understates how much of the product exists.

Where this definition comes from: audits/target-architecture/APP-SUMMARY-PROPOSED.md — OpenCV, YOLO/ONNX, SAM2, PaddleOCR, plus local Ollama, RAG and Whisper.

Code: Code exists — Found in the repositories by the architecture review.

In the plan: M7 · Reaching inward: remote command and local AI access — 0 of 19 done, 68h, which also builds Remote update and command. open the 19 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

Plant databaseM5 · 0 of 18 done

The plant's own database Not on the board

Everything the site records — inspections, recipes, users, machines — held in an encrypted database on the plant machine. Forty tables.

Two additions are needed and neither exists: a customer id on every record, and an outbox so results can be sent onward safely.

Where this definition comes from: APP-SUMMARY-PROPOSED.md §3.2, verified against the code.

Code: Exists, needs changing — Code is there; this programme changes it.

In the plan: M5 · Outbox, retention and the thin vertical slice — 0 of 18 done, 67h, which also builds API Gateway, Analytics. open the 18 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

Operator app58% done

Certainty Client In test

The app the operator uses on the factory floor — the screens for running an inspection, seeing results and administering the site.

Carries the security work: today it talks to Core in cleartext over the plant network.

Where this definition comes from: Derived from its 21 tickets — the site admin dashboard, robotics movement and capture points — plus the architecture review, which identifies it as a Flutter app served from Core.

Code: Code exists — Found in the repositories by the architecture review.

Epics: INTEL-39

In the plan: M1 · Critical remediation and distribution unblock — 0 of 21 done, 66h, which also builds Certainty Web; M2 · Transport security, key escrow and the recipe boundary — 0 of 30 done, 126h, which also builds Certainty Core, Key escrow; REL - Release and distribution — 0 of 17 done, 63h, which also builds Licence Portal, Remote update and command. open the 68 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

  • INTEL-106 Live plant credentials committed to the repository (incomplete scrub)Done
  • INTEL-107 develop fails flutter analyze and 2 tests; broken import hides 9 test Testing
  • INTEL-108 Release builds signed with the public Android debug keystore -- blocksTesting
  • INTEL-109 Cleartext HTTP globally enabled; credentials and imagery readable on tDone
  • INTEL-110 Web builds store the JWT and device clientSecret in plaintext localStoTesting
  • INTEL-111 Secret-hygiene gaps: .gitignore misses the paths the project's own docDone
  • INTEL-112 No CI has ever existed, while a working quality gate sits unwiredDone
  • INTEL-113 Test coverage 28.49%, concentrated not targeted; suite requires a liveTo Do
  • INTEL-114 Two live UI defects: stale values submitted silently, and an orphaned To Do
  • INTEL-115 Documentation and governance drift: authoritative docs point at contenDone
  • INTEL-116 Auth model gaps: device-scoped WebSocket auth and fail-open session vaDone
  • INTEL-117 Architecture and dependency debt (non-blocking)Done
  • INTEL-156 Admin dashboards render hardcoded sample data with nothing in the UI tTo Do
  • INTEL-314 Client imaging screen dynamic renderingTesting
  • and 7 more
Licence PortalM10, REL · 0 of 41 done

Licence Portal Not on the board

Where Intelgic issues and manages customer licences — who has bought what, how many machines they may run it on.

Its epic is marked Done with no tickets underneath it at all. The licence work is really happening inside Certainty Web.

Where this definition comes from: APP-SUMMARY-PROPOSED.md — a Flutter web app against the entitlement service.

Code: Code exists — Found in the repositories by the architecture review.

Epics: INTEL-205

In the plan: M10 · Cloud control plane: admin, tenancy and payment status — 0 of 24 done, 72h, which also builds API Gateway, Who is allowed to do what; REL - Release and distribution — 0 of 17 done, 63h, which also builds Certainty Client, Remote update and command. open the 41 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

API Gateway0% done

API Gateway Not started

The single front door everything else talks through. Nothing reaches the cloud without passing it.

Where this definition comes from: Derived from its 3 tickets, all of which are design rather than build, and APP-SUMMARY-PROPOSED.md §2.

Code: Does not exist yet — No code in any repository.

Epics: INTEL-294

In the plan: M10 · Cloud control plane: admin, tenancy and payment status — 0 of 24 done, 72h, which also builds Licence Portal, Who is allowed to do what; M5 · Outbox, retention and the thin vertical slice — 0 of 18 done, 67h, which also builds Analytics, The plant's own database. open the 42 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

  • INTEL-305 Design the API Gateway architectureTo Do
  • INTEL-306 Build the Gateway with authentication readyTo Do
  • INTEL-307 Make the Gateway observable and safe to operateTo Do
Multi-tenantM3 · 0 of 20 done

Multi-tenant setup Not on the board

Keeping each customer's data and access separate inside one shared back end. Without it, one back end cannot safely serve two customers.

There is no epic and no ticket for this anywhere on the board. It is a blocker that is currently invisible in every progress figure.

Where this definition comes from: Named by Lindsey as a precondition for deploying: “The multi-tenant is set up so we can deploy. And then we can start pushing the servers.”

Code: Does not exist yet — No code in any repository.

In the plan: M3 · Tenant and entitlement — 0 of 20 done, 72h, which also builds Certainty Core, Entitlement service. open the 20 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

LicencesM3 · 0 of 20 done

Entitlement service Not on the board

The system of record for licences and seats — which machines are allowed to run Certainty, and how many.

Built, and tracked under Certainty Web rather than under the Licence Portal epic.

Where this definition comes from: APP-SUMMARY-PROPOSED.md §3.1 — eight tables today, verified from the database migrations.

Code: Exists, needs changing — Code is there; this programme changes it.

In the plan: M3 · Tenant and entitlement — 0 of 20 done, 72h, which also builds Certainty Core, Multi-tenant setup. open the 20 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

AnalyticsM5, M6 · 0 of 37 done

Analytics Not on the board

Inspection history kept beyond what the plant machine can hold, one database per customer, so trends can be asked about over months.

Where this definition comes from: APP-SUMMARY-PROPOSED.md §3.3, carried from Intelgic's own architecture as a customer commitment.

Code: Does not exist yet — No code in any repository.

In the plan: M5 · Outbox, retention and the thin vertical slice — 0 of 18 done, 67h, which also builds API Gateway, The plant's own database; M6 · Analytics service — 0 of 19 done, 74h. open the 37 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

MonitoringM4 · 0 of 27 done

Observability Not on the board

Knowing that a plant machine is healthy, and being told when it is not, without phoning the customer.

Where this definition comes from: APP-SUMMARY-PROPOSED.md §2 — logs, metrics and fault grouping.

Code: Does not exist yet — No code in any repository.

In the plan: M4 · Remote monitoring and fault reporting — 0 of 27 done, 97h, which also builds Certainty Core. open the 27 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

Remote updateM7, REL · 0 of 36 done

Remote update and command Not on the board

Sending a new version or an instruction to a site without anyone travelling there. The plant asks the cloud for work; the cloud never reaches in.

This is the capability the whole back-end push is for.

Where this definition comes from: APP-SUMMARY-PROPOSED.md decision 5.5. Taylor: “the front ends aren't even installed to where we can remote deploy at all.”

Code: Awaiting a decision — Design decision recorded, not yet made.

In the plan: M7 · Reaching inward: remote command and local AI access — 0 of 19 done, 68h, which also builds The vision and AI stack; REL - Release and distribution — 0 of 17 done, 63h, which also builds Certainty Client, Licence Portal. open the 36 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

Fleet viewnot scoped

Fleet management Not on the board

Seeing every customer site at once — which are healthy, which are behind, which need attention — rather than one at a time.

Where this definition comes from: audits/target-architecture/MOTHERSHIP-HOW-IT-WORKS.md. Scoped as Engagement 2, which has not been bought.

Code: Does not exist yet — No code in any repository.

In the plan: no milestone covers this, because it is Engagement 2 work and Engagement 2 has not been bought — so a zero here is a commercial fact, not a team that is behind.

No developer ticket on the board tracks this one. The plan line above is what there is.

What may leavenot scoped

What may leave a customer's site Not on the board

An explicit gate deciding what data is allowed to leave a factory. The stated commitment is that defect information may cross and pictures never do.

Where this definition comes from: MOTHERSHIP-HOW-IT-WORKS.md and APP-SUMMARY-TARGET.md.

Code: Does not exist yet — No code in any repository.

In the plan: no milestone covers this, because it is Engagement 2 work and Engagement 2 has not been bought — so a zero here is a commercial fact, not a team that is behind.

No developer ticket on the board tracks this one. The plan line above is what there is.

Read it top-down. The platform is the top row — that is what works today, and it is what the word means when the team says “the platform”. Everything below is being integrated into it: the people who use it, the cloud being built now, and the fleet view that comes last. Arrows are what talks to what. Hover a box for what it is and the tickets behind it; click it to jump to its full entry underneath.

Every piece, floor by floor

The same platform in full, with the definition behind every box and the tickets behind every colour.

Not startedIn progressBlockedIn testDone on the boardNot on the board

Hover or tap any box for what it is, where that definition came from, and the tickets behind its colour. A box showing a percentage is measured from its own developer tickets. A box showing a milestone code instead — M7 · 0 of 19 done — has no ticket of its own, so what is quoted is the scope of the milestone that builds it. A milestone usually builds several boxes, so those counts cannot be added up down the page; the two figures are not the same measure and are deliberately written differently.

The platform — one of these per factory

This is the platform itself, and the part that works today. Everything below it is being integrated into it.

1 of 5 pieces at or past test

Certainty Core

The inspection engine that sits in the factory. It talks to the cameras, the lasers and the machines on the line, runs…

49% doneCode exists
M3M4M2

Certainty Core In test

The inspection engine that sits in the factory. It talks to the cameras, the lasers and the machines on the line, runs the inspection, and decides pass or fail.

The single most complete thing on the board, and the reason a demo can be given at all.

Where this definition comes from: Derived from its 49 tickets — OPC UA, SCADA, 3D profilers, the defect-detection pipeline — and matches the architecture review's description of a .NET service on the plant machine.

Code: Code exists — Found in the repositories by the architecture review.

Epics: INTEL-38

In the plan: M3 · Tenant and entitlement — 0 of 20 done, 72h, which also builds Entitlement service, Multi-tenant setup; M4 · Remote monitoring and fault reporting — 0 of 27 done, 97h, which also builds Observability; M2 · Transport security, key escrow and the recipe boundary — 0 of 30 done, 126h, which also builds Certainty Client, Key escrow. open the 77 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

  • INTEL-104 [kunald-intelgic] Activity LogDone
  • INTEL-143 Vision pipeline exec()s Python named by a recipe, and the comment callTo Do
  • INTEL-144 Seventeen unbound names in authored Python -- NameError at runtime in Done
  • INTEL-145 flutter_web/ is 40MB of committed build output and the application bunDone
  • INTEL-147 No CI -- fourth repository, fourth time, and this one has the most to Done
  • INTEL-148 Restore is not reproducible -- no SDK pin, no lockfile, and four declaDone
  • INTEL-149 174 build warnings, including 132 platform-compatibility warnings agaiTo Do
  • INTEL-150 Losing sqlite-key.enc makes the encrypted database permanently unreadaDone
  • INTEL-151 No Python lint configuration exists, so there is no agreed standard toTo Do
  • INTEL-152 Only a dev branch exists -- the three-branch model has not reached thiDone
  • INTEL-153 About 152MB of vendor SDK binaries committed to gitTo Do
  • INTEL-154 Swagger unauthenticated when enabled, BOM breaks .gitattributes, orphaTo Do
  • INTEL-244 Activity LogPush to Dev
  • INTEL-259 Hardware ManagementPush to Dev
  • and 35 more
The vision and AI stack

The part that actually looks at the picture: the models that spot a defect, read a label, or measure a part. It runs o…

M7 · 0 of 19 doneCode exists
M7

The vision and AI stack Not on the board

The part that actually looks at the picture: the models that spot a defect, read a label, or measure a part. It runs on the plant machine, not in the cloud.

No epic covers it. It is built, and invisible on the board — so a chart of tickets understates how much of the product exists.

Where this definition comes from: audits/target-architecture/APP-SUMMARY-PROPOSED.md — OpenCV, YOLO/ONNX, SAM2, PaddleOCR, plus local Ollama, RAG and Whisper.

Code: Code exists — Found in the repositories by the architecture review.

In the plan: M7 · Reaching inward: remote command and local AI access — 0 of 19 done, 68h, which also builds Remote update and command. open the 19 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

Dynamic camera exposure

Photographs each part several times at different brightnesses, so a shiny or dark surface is still readable. Without i…

81% doneCode exists

Dynamic camera exposure In progress

Photographs each part several times at different brightnesses, so a shiny or dark surface is still readable. Without it, half the defects are invisible to the camera.

Nearly finished. No architecture document mentions it at all.

Where this definition comes from: Derived from its 15 tickets — the exposure bracket planner, and showing one representative frame per bracket rather than all of them.

Code: Code exists — Found in the repositories by the architecture review.

Epics: INTEL-321

In the plan: no milestone in the estimate maps to this component, so the plan says nothing about it either way. Whether that is a gap in the estimate or work genuinely outside it has not been settled.

  • INTEL-334 Fix captures-root path traversal guard in imaging endpointsDone
  • INTEL-335 Frame-level exposure telemetry on the MindVision capture pathDone
  • INTEL-336 ExposureBracketPlanner — pure ladder computation, unit testedDone
  • INTEL-337 MindVisionBracketRunner and BracketOptionsDone
  • INTEL-338 Capture sidecar schema v2 with exposure and bracket blocksDone
  • INTEL-339 Consolidate the two history implementations, then extend once for bracDone
  • INTEL-340 Imaging capabilities endpoint and the bracket_capture socket routeDone
  • INTEL-341 Write the imaging bracket protocol spec for the Flutter repoDone
  • INTEL-354 Move the bracket trigger from the client to an imaging-bracket.json flDone
  • INTEL-357 A stale frame latches the confirm countdown, so SettleConfirmFrames reDone
  • INTEL-358 A bracket rung whose target equals the camera's current exposure neverDone
  • INTEL-360 A bracket refused as camera_busy falls back to a frame another bracketDone
  • INTEL-361 Test client's exposure-restore verdict reads an un-awaited capabilitieDone
  • INTEL-362 StopCameraAsync destroys a MindVision settings session before checkingTo Do
  • and 7 more
SOP monitoring

Watches a person carry out a written procedure across several cameras and judges each step, then the job as a whole. T…

50% doneCode exists

SOP monitoring In progress

Watches a person carry out a written procedure across several cameras and judges each step, then the job as a whole. This is the capability Bobrick is buying.

Where this definition comes from: Derived from its 4 tickets — multi-camera integration, a multi-region rule engine, and a runtime screen with step-wise and final decisions.

Code: Code exists — Found in the repositories by the architecture review.

Epics: INTEL-295

In the plan: no milestone in the estimate maps to this component, so the plan says nothing about it either way. Whether that is a gap in the estimate or work genuinely outside it has not been settled.

  • INTEL-308 Multi-camera integration with the SOP pipelineDone
  • INTEL-309 Multi-model integration with the SOP pipelineDone
  • INTEL-310 Multi-camera, multi-region, multi-detection rule engineTo Do
  • INTEL-311 Multi-feed runtime screen with step-wise and final decisionsTo Do
The plant's own database

Everything the site records — inspections, recipes, users, machines — held in an encrypted database on the plant machi…

M5 · 0 of 18 doneExists, needs changing
M5

The plant's own database Not on the board

Everything the site records — inspections, recipes, users, machines — held in an encrypted database on the plant machine. Forty tables.

Two additions are needed and neither exists: a customer id on every record, and an outbox so results can be sent onward safely.

Where this definition comes from: APP-SUMMARY-PROPOSED.md §3.2, verified against the code.

Code: Exists, needs changing — Code is there; this programme changes it.

In the plan: M5 · Outbox, retention and the thin vertical slice — 0 of 18 done, 67h, which also builds API Gateway, Analytics. open the 18 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

The people who use it

What an operator, a plant manager and a customer admin actually open.

3 of 4 pieces at or past test

Certainty Client

The app the operator uses on the factory floor — the screens for running an inspection, seeing results and administeri…

58% doneCode exists
M1M2REL

Certainty Client In test

The app the operator uses on the factory floor — the screens for running an inspection, seeing results and administering the site.

Carries the security work: today it talks to Core in cleartext over the plant network.

Where this definition comes from: Derived from its 21 tickets — the site admin dashboard, robotics movement and capture points — plus the architecture review, which identifies it as a Flutter app served from Core.

Code: Code exists — Found in the repositories by the architecture review.

Epics: INTEL-39

In the plan: M1 · Critical remediation and distribution unblock — 0 of 21 done, 66h, which also builds Certainty Web; M2 · Transport security, key escrow and the recipe boundary — 0 of 30 done, 126h, which also builds Certainty Core, Key escrow; REL - Release and distribution — 0 of 17 done, 63h, which also builds Licence Portal, Remote update and command. open the 68 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

  • INTEL-106 Live plant credentials committed to the repository (incomplete scrub)Done
  • INTEL-107 develop fails flutter analyze and 2 tests; broken import hides 9 test Testing
  • INTEL-108 Release builds signed with the public Android debug keystore -- blocksTesting
  • INTEL-109 Cleartext HTTP globally enabled; credentials and imagery readable on tDone
  • INTEL-110 Web builds store the JWT and device clientSecret in plaintext localStoTesting
  • INTEL-111 Secret-hygiene gaps: .gitignore misses the paths the project's own docDone
  • INTEL-112 No CI has ever existed, while a working quality gate sits unwiredDone
  • INTEL-113 Test coverage 28.49%, concentrated not targeted; suite requires a liveTo Do
  • INTEL-114 Two live UI defects: stale values submitted silently, and an orphaned To Do
  • INTEL-115 Documentation and governance drift: authoritative docs point at contenDone
  • INTEL-116 Auth model gaps: device-scoped WebSocket auth and fail-open session vaDone
  • INTEL-117 Architecture and dependency debt (non-blocking)Done
  • INTEL-156 Admin dashboards render hardcoded sample data with nothing in the UI tTo Do
  • INTEL-314 Client imaging screen dynamic renderingTesting
  • and 7 more
Certainty Web

Named as the browser version of Core's screens. Most of its work so far has been the security tightening the platform …

91% doneExists, needs changing
M1

Certainty Web In test

Named as the browser version of Core's screens. Most of its work so far has been the security tightening the platform needed — closing the findings from the code audit — plus the licence back end.

The security work was necessary and is real progress. The care needed is only in reading the number: this epic is the closest to done on the board, and that is hardening finished, not the web product finished.

Where this definition comes from: Derived from its tickets: of 32, only INTEL-48 is about web screens; the rest are audit remediation and licensing.

Code: Exists, needs changing — Code is there; this programme changes it.

Epics: INTEL-40

In the plan: M1 · Critical remediation and distribution unblock — 0 of 21 done, 66h, which also builds Certainty Client. open the 21 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

  • INTEL-118 Application does not build -- CardTheme/CardThemeData type error blockDone
  • INTEL-119 No SDK pin; declared Dart constraint understates what actually resolveDone
  • INTEL-120 pubspec.lock contradicts pubspec.yaml -- SSO removal was half-completeDone
  • INTEL-121 Test suite: 32 pass, 37 fail; one file never loads; tests assert removDone
  • INTEL-122 Session identity and role are read from browser storage without serverDone
  • INTEL-123 /admin route has no role guard; any authenticated user can load the adDone
  • INTEL-124 Public registration accepts an arbitrary role on an unauthenticated enDone
  • INTEL-125 No CI, no analysis_options.yaml, and bin/eh does not existTo Do
  • INTEL-126 Token refresh is broken and never invoked; no 401 handling anywhereDone
  • INTEL-127 Tokens stored in browser localStorage on web, with no CSPDone
  • INTEL-128 .env ships as a public web asset, and the house docs teach putting APIDone
  • INTEL-129 eng-os/ governance was copied from certainty-client and describes a diDone
  • INTEL-130 Correctness bugs: customer list crash, stubbed validation shipped as aDone
  • INTEL-131 Dead code, hardcoded colours, doc drift, and committed generated filesDone
  • and 18 more
Licence Portal

Where Intelgic issues and manages customer licences — who has bought what, how many machines they may run it on.

M10, REL · 0 of 41 doneCode exists
M10REL

Licence Portal Not on the board

Where Intelgic issues and manages customer licences — who has bought what, how many machines they may run it on.

Its epic is marked Done with no tickets underneath it at all. The licence work is really happening inside Certainty Web.

Where this definition comes from: APP-SUMMARY-PROPOSED.md — a Flutter web app against the entitlement service.

Code: Code exists — Found in the repositories by the architecture review.

Epics: INTEL-205

In the plan: M10 · Cloud control plane: admin, tenancy and payment status — 0 of 24 done, 72h, which also builds API Gateway, Who is allowed to do what; REL - Release and distribution — 0 of 17 done, 63h, which also builds Certainty Client, Remote update and command. open the 41 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

User manual

The product documentation a customer is given.

100% doneDoes not exist yet

User manual Done on the board

The product documentation a customer is given.

Where this definition comes from: One ticket exists. Lindsey: “user manual, I'm not overly concerned with. That comes as you build a product.”

Code: Does not exist yet — No code in any repository.

Epics: INTEL-41

In the plan: no milestone in the estimate maps to this component, so the plan says nothing about it either way. Whether that is a gap in the estimate or work genuinely outside it has not been settled.

  • INTEL-60 [MadhuSudanM-Intelgic] DOC: Certainty AI Tech DocDone

The cloud — the part that lets you run many customers at once

This is the layer Lindsey means by “we're two weeks behind on the back end”. Almost none of it exists yet, and until it does, every customer site is an island that somebody has to visit.

1 of 9 pieces at or past test

API Gateway

The single front door everything else talks through. Nothing reaches the cloud without passing it.

0% doneDoes not exist yet
M10M5

API Gateway Not started

The single front door everything else talks through. Nothing reaches the cloud without passing it.

Where this definition comes from: Derived from its 3 tickets, all of which are design rather than build, and APP-SUMMARY-PROPOSED.md §2.

Code: Does not exist yet — No code in any repository.

Epics: INTEL-294

In the plan: M10 · Cloud control plane: admin, tenancy and payment status — 0 of 24 done, 72h, which also builds Licence Portal, Who is allowed to do what; M5 · Outbox, retention and the thin vertical slice — 0 of 18 done, 67h, which also builds Analytics, The plant's own database. open the 42 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

  • INTEL-305 Design the API Gateway architectureTo Do
  • INTEL-306 Build the Gateway with authentication readyTo Do
  • INTEL-307 Make the Gateway observable and safe to operateTo Do
Multi-tenant setup

Keeping each customer's data and access separate inside one shared back end. Without it, one back end cannot safely se…

M3 · 0 of 20 doneDoes not exist yet
M3

Multi-tenant setup Not on the board

Keeping each customer's data and access separate inside one shared back end. Without it, one back end cannot safely serve two customers.

There is no epic and no ticket for this anywhere on the board. It is a blocker that is currently invisible in every progress figure.

Where this definition comes from: Named by Lindsey as a precondition for deploying: “The multi-tenant is set up so we can deploy. And then we can start pushing the servers.”

Code: Does not exist yet — No code in any repository.

In the plan: M3 · Tenant and entitlement — 0 of 20 done, 72h, which also builds Certainty Core, Entitlement service. open the 20 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

Entitlement service

The system of record for licences and seats — which machines are allowed to run Certainty, and how many.

M3 · 0 of 20 doneExists, needs changing
M3

Entitlement service Not on the board

The system of record for licences and seats — which machines are allowed to run Certainty, and how many.

Built, and tracked under Certainty Web rather than under the Licence Portal epic.

Where this definition comes from: APP-SUMMARY-PROPOSED.md §3.1 — eight tables today, verified from the database migrations.

Code: Exists, needs changing — Code is there; this programme changes it.

In the plan: M3 · Tenant and entitlement — 0 of 20 done, 72h, which also builds Certainty Core, Multi-tenant setup. open the 20 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

Who is allowed to do what

Roles and permissions, enforced on the server rather than merely hidden in the app.

0% doneDoes not exist yet
M10M8

Who is allowed to do what In progress

Roles and permissions, enforced on the server rather than merely hidden in the app.

Where this definition comes from: Derived from its 12 tickets — seeing only what your role allows, enforcing roles server-side, and blocking deletion of a role that still has users.

Code: Does not exist yet — No code in any repository.

Epics: INTEL-293

In the plan: M10 · Cloud control plane: admin, tenancy and payment status — 0 of 24 done, 72h, which also builds API Gateway, Licence Portal; M8 · Identity standardisation — 0 of 18 done, 72h, which also builds Single sign-on. open the 42 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

  • INTEL-301 Manage users and roles from within the clientTo Do
  • INTEL-302 See only what my role allowsTo Do
  • INTEL-303 Enforce roles on the server, not just in the UITo Do
  • INTEL-304 Migrate existing users onto the role modelTo Do
  • INTEL-503 Role-Based Permission Backend on Server SideIn Progress
Single sign-on

Letting a customer's staff sign in with their own company login instead of another separate password.

0% doneDoes not exist yet
M8

Single sign-on In test

Letting a customer's staff sign in with their own company login instead of another separate password.

Where this definition comes from: Derived from its 4 tickets — one unified identity, and configuring an organisation's own identity provider.

Code: Does not exist yet — No code in any repository.

Epics: INTEL-292

In the plan: M8 · Identity standardisation — 0 of 18 done, 72h, which also builds Who is allowed to do what. open the 18 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

  • INTEL-297 Sign in to the Certainty Client with a single, unified identityTesting
  • INTEL-298 Configure an organization's own identity providerTesting
  • INTEL-299 End a session cleanly, everywhere it existsTesting
  • INTEL-300 Map SSO identities to Certainty user recordsTo Do
  • INTEL-536 [Backend] Exchange an SSO id_token for a Certainty token (POST /auth/sTesting
  • INTEL-542 [Backend] Harden SSO against token replay with a server-issued nonceTo Do
Analytics

Inspection history kept beyond what the plant machine can hold, one database per customer, so trends can be asked abou…

M5, M6 · 0 of 37 doneDoes not exist yet
M5M6

Analytics Not on the board

Inspection history kept beyond what the plant machine can hold, one database per customer, so trends can be asked about over months.

Where this definition comes from: APP-SUMMARY-PROPOSED.md §3.3, carried from Intelgic's own architecture as a customer commitment.

Code: Does not exist yet — No code in any repository.

In the plan: M5 · Outbox, retention and the thin vertical slice — 0 of 18 done, 67h, which also builds API Gateway, The plant's own database; M6 · Analytics service — 0 of 19 done, 74h. open the 37 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

Observability

Knowing that a plant machine is healthy, and being told when it is not, without phoning the customer.

M4 · 0 of 27 doneDoes not exist yet
M4

Observability Not on the board

Knowing that a plant machine is healthy, and being told when it is not, without phoning the customer.

Where this definition comes from: APP-SUMMARY-PROPOSED.md §2 — logs, metrics and fault grouping.

Code: Does not exist yet — No code in any repository.

In the plan: M4 · Remote monitoring and fault reporting — 0 of 27 done, 97h, which also builds Certainty Core. open the 27 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

Remote update and command

Sending a new version or an instruction to a site without anyone travelling there. The plant asks the cloud for work; …

M7, REL · 0 of 36 doneAwaiting a decision
M7REL

Remote update and command Not on the board

Sending a new version or an instruction to a site without anyone travelling there. The plant asks the cloud for work; the cloud never reaches in.

This is the capability the whole back-end push is for.

Where this definition comes from: APP-SUMMARY-PROPOSED.md decision 5.5. Taylor: “the front ends aren't even installed to where we can remote deploy at all.”

Code: Awaiting a decision — Design decision recorded, not yet made.

In the plan: M7 · Reaching inward: remote command and local AI access — 0 of 19 done, 68h, which also builds The vision and AI stack; REL - Release and distribution — 0 of 17 done, 63h, which also builds Certainty Client, Licence Portal. open the 36 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

Key escrow

A safe copy of the key that unlocks a plant database, so a dead machine does not take a customer's data with it.

M2 · 0 of 30 doneAwaiting a decision
M2

Key escrow Not on the board

A safe copy of the key that unlocks a plant database, so a dead machine does not take a customer's data with it.

Where this definition comes from: APP-SUMMARY-PROPOSED.md decision 5.4.

Code: Awaiting a decision — Design decision recorded, not yet made.

In the plan: M2 · Transport security, key escrow and the recipe boundary — 0 of 30 done, 126h, which also builds Certainty Client, Certainty Core. open the 30 cards. None of them has been started yet. These counts belong to the milestone, not to this box on its own.

No developer ticket on the board tracks this one. The plan line above is what there is.

The fleet — many plants, one view

What it becomes once more than one factory is running. None of this is built, and it is deliberately the last thing, not the first.

0 of 2 pieces at or past test

Fleet management

Seeing every customer site at once — which are healthy, which are behind, which need attention — rather than one at a …

not scopedDoes not exist yet

Fleet management Not on the board

Seeing every customer site at once — which are healthy, which are behind, which need attention — rather than one at a time.

Where this definition comes from: audits/target-architecture/MOTHERSHIP-HOW-IT-WORKS.md. Scoped as Engagement 2, which has not been bought.

Code: Does not exist yet — No code in any repository.

In the plan: no milestone covers this, because it is Engagement 2 work and Engagement 2 has not been bought — so a zero here is a commercial fact, not a team that is behind.

No developer ticket on the board tracks this one. The plan line above is what there is.

What may leave a customer's site

An explicit gate deciding what data is allowed to leave a factory. The stated commitment is that defect information ma…

not scopedDoes not exist yet

What may leave a customer's site Not on the board

An explicit gate deciding what data is allowed to leave a factory. The stated commitment is that defect information may cross and pictures never do.

Where this definition comes from: MOTHERSHIP-HOW-IT-WORKS.md and APP-SUMMARY-TARGET.md.

Code: Does not exist yet — No code in any repository.

In the plan: no milestone covers this, because it is Engagement 2 work and Engagement 2 has not been bought — so a zero here is a commercial fact, not a team that is behind.

No developer ticket on the board tracks this one. The plan line above is what there is.

Ordered the way the team talks about it: the platform first, then everything being folded into it, ending with the fleet view nobody has bought. Reading down the page is reading forward in time.

The licensing data model

Same colours: green exists today, grey is added by this programme. This is the database behind who has bought what and which machines they may run it on.

customersexists today

A company that has bought Certainty.

  • customer_id
  • company_name
  • email
  • country
  • holds licenses
  • employs users
plansexists today

A template: how many machines and how long.

  • plan_id
  • plan_name
  • default_hosts
  • default_expiry_days
  • templates licenses
licensesexists today

What one customer actually bought.

  • license_id
  • license_key
  • customer_id
  • total_hosts
  • used_hosts
  • expiry_date
  • activated on license_hosts
  • issues offline_activation_codes
license_hostsdoes not exist yet

One row per machine using a seat. The change that makes seat management possible at all.

  • id
  • license_id
  • installation_id
  • first_seen
  • last_seen
  • revoked_at
offline_activation_codesexists today

Activating a machine with no internet — normal in a factory.

  • id
  • activation_code
  • license_id
  • machine_id
installationsdoes not exist yet

A running installation and when it was last heard from. What the monitoring screens would read.

  • installation_id
  • customer_id
  • core_version
  • last_heartbeat
  • claims license_hosts
  • escrows to key_escrow
key_escrowdoes not exist yet

The safe copy of a site's database key.

  • installation_id
  • wrapped_key
  • escrowed_at

Referenced but not detailed here: users — in the source document but outside the eight tables read from the migrations.

For the plain-language version of all of this — what each piece is for, who is buying which capability, and what the system keeps — see The product.

Timeline

One bar per project (epic), snapshot of 2026-09-16. A bar starts at the first issue created under the project and runs to the snapshot date, or to its last closed issue if nothing is left open. The colours inside a bar are the share of its issues in each status, not how much time has passed. Very few issues on this board carry planned dates, so bars show recorded work, not a plan. Use the tabs to switch project group; hover a bar for its counts.

Done In progress / testing / push to dev Not started Removed or rejected Stated target date Programme date (1 Oct, 15 Oct, 1 Nov)
17 Aug
24 Aug
31 Aug
07 Sep
14 Sep
21 Sep
28 Sep
05 Oct
12 Oct
19 Oct
26 Oct
02 Nov
INTEL-38 Certainty Core 49% · To Do
INTEL-40 Certainty Web 91% · To Do
INTEL-39 Certainty Client 52% · To Do
INTEL-41 Certainty User Manual 100% · To Do
INTEL-292 SSO for Certainty Client 0% · In Progress
INTEL-293 Role-Based User Management 0% · To Do
INTEL-295 SOP Monitoring 50% · In Progress
INTEL-294 API Gateway Layer 0% · To Do
INTEL-321 Dynamic Camera Exposure 81% · Done
INTEL-43 Bobrick VAAV 100% · To Do
INTEL-206 Reliant Cellular 0% · Backlog
INTEL-212 Stakes MFG 0% · Backlog
INTEL-283 Kalpataru 100% · Done
INTEL-296 Dynamic Defect Types (Stakes) 0% · To Do
INTEL-346 Bobrick (3) 100% · Done
INTEL-359 Polyplex 5% · To Do
INTEL-348 Reynolds Tobacco 0% · To Do
INTEL-355 IntelgicPOC 0% · To Do
INTEL-42 Demo Setup 100% · To Do
snapshot 09-16
10-01
10-15
11-01

Customer work, by stage rather than by date

Every customer delivery in the same five stages as the Completion view. Bar length is the amount of work, and the colours are where it has got to.

Polyplex: To do 35, Done 2; Reliant Cellular: To do 18, In QA 1; Stakes MFG: To do 15; Reynolds Tobacco: To do 5; Kalpataru: Done 3; Bobrick VAAV: Done 1; Bobrick (3): Done 1; Dynamic Defect Types (Stakes): To do 1PolyplexTo do: 3535Done: 237Reliant CellularTo do: 1818In QA: 119Stakes MFGTo do: 151515Reynolds TobaccoTo do: 555KalpataruDone: 333Bobrick VAAVDone: 111Bobrick (3)Done: 111Dynamic Defect Types (StakTo do: 111To doIn progressIn QABlockedDone

Can 1 November be made?

Measured from the 2026-09-16 snapshot: 46 days, or about 6.6 weeks, to the contractual date.

2026-10-01

15days
Stage 0 / Stage A — make the platform safe to change
estimated

2026-10-15

29days
Investor raise
committed

2026-11-01

46days
Contractual date — Engagement 1 committed scope
committed

What has actually been closed, week by week

issues closed per week: W34 34, W35 0, W36 38, W37 75, W38 2603875W34: 34W35: 0W36: 38W37: 75W38: 26W34W35W36W37W38

Stories, tasks and bugs closed in each week, counted by their resolution date. The flat week is real: nothing was closed in W35.

Required against observed

Needed each week

73items
481 still open, 6.6 weeks left

Closed each week so far

35average
across 5 weeks, range 0 to 75

Neither number is coloured, because neither is good or bad on its own: one is an arithmetic requirement and the other is a record of closures, and the weeks behind that average are 34, 0, 38, 75, 26 — a spread wide enough that the mean is a weak thing to plan on.

Why this is not a forecast, and what would make it one

Counted by the week each issue's resolution date falls in, from the same Jira snapshot the rest of this page reads. It is history recovered from one collection, not a trend measured across weekly runs -- only one of those has happened.

  • A resolution date records when a ticket was closed, not when the work was done. Eleven days in this project carry a bulk-edit fingerprint, so some closures are bookkeeping catching up rather than delivery.
  • Tickets closed before they were ever tracked here still count in the week they were closed.

A burn-up with a projection line needs movement measured across weekly collections. One has happened. The second run, on the next Friday, is the first point at which a trend can be drawn at all — and no line is drawn here from a single point, because it would be a drawing rather than a measurement.

The four things that actually decide it

  • The board is not the committed scope.
    The contractual date covers 211 stories and 573.5 hours of Engagement 1 scope. This board holds 635 live items across every customer and every internal workstream, and nobody has mapped one onto the other. The rate above is therefore the right shape and the wrong population.
  • Most of the remaining work belongs to nobody.
    265 open items have no assignee, 150 of them in one customer backlog. Work that is not assigned is not scheduled, and an average closure rate assumes someone is doing it.
  • The plan’s start date did not happen.
    Engagement 1 was drawn from a 2 September start. That start slipped while the architecture question was settled, and the plan holds two weeks of margin that the documents describe as testing time rather than slack.
  • Two developers or three is still unreconciled.
    The scope document says three developers puts the committed scope inside 1 November; the estimate’s own cover disclaimer says two. Both are stated as fact in the same set of documents. The answer changes the date.

Known problems with the plan these dates come from

Carried from the estimate documents unresolved. Picking a side here would invent a decision nobody has made.

  • The schedule's start date did not happen. PROGRAM-SUMMARY.md:573-576 - 'Engagement 1 assumed a start on 2 September. That has not happened, and the margin is being spent while the design question is settled.' Any plan line drawn from 2 September is already counterfactual.
  • Two developers or three? SCOPE.md:330 and PROGRAM-SUMMARY.md:566 say three; the estimate.json cover disclaimer and SCOPE.md:404 (assumption A-06) say two. Both are stated as what puts the committed scope inside 1 November. Unreconciled.
  • The two Gantt charts disagree on their own start date - 2026-09-02 in WHOLE-SHAPE.md, 2026-09-03 in PROGRAM-SUMMARY.md.
  • Three different September release dates appear in one call (_context/day-2026-09-08.md:27-32): 23rd, 25th and 26th. The transcript is self-contradictory; none is treated as confirmed.

Segment by segment

Progress counts top-level issues only; sub-tasks are shown separately so a segment that breaks work down is not ranked above one that does not. "Unsegmented" is work belonging to no epic — listed, not filtered out. Every epic key links straight to Jira.

Certainty product i

Certainty Core: 24 of 49; Certainty Web: 29 of 32; Certainty Client: 11 of 21; Dynamic Camera Exposure: 17 of 21; SSO for Certainty Client: 0 of 6; Role-Based User Management: 0 of 5; SOP Monitoring: 2 of 4; API Gateway Layer: 0 of 3; Certainty User Manual: 1 of 1Certainty Core24/49Certainty Web29/32Certainty Client11/21Dynamic Camera Exposure17/21SSO for Certainty Client0/6Role-Based User Management0/5SOP Monitoring2/4API Gateway Layer0/3Certainty User Manual1/1
EpicSegmentProgress iSub-tasks iUnassigned iEpic statusFlags
INTEL-38 Certainty Core i 24/49 (49%) 4 5 To Do 26
INTEL-40 Certainty Web i 29/32 (91%) 1 To Do 3
INTEL-39 Certainty Client i 11/21 (52%) 1 To Do 6
INTEL-321 Dynamic Camera Exposure i 17/21 (81%) 3 Done 1
INTEL-292 SSO for Certainty Client i 0/6 (0%) In Progress 4
INTEL-293 Role-Based User Management i 0/5 (0%) 7 4 To Do 1
INTEL-295 SOP Monitoring i 2/4 (50%) 2 In Progress 1
INTEL-294 API Gateway Layer i 0/3 (0%) 3 To Do 1
INTEL-41 Certainty User Manual i 1/1 (100%) To Do

Customer deployments i

Polyplex: 2 of 37; Reliant Cellular: 0 of 19; Stakes MFG: 0 of 15; Reynolds Tobacco: 0 of 5; Kalpataru: 3 of 3; Bobrick VAAV: 1 of 1; Bobrick (3): 1 of 1; Dynamic Defect Types (Stakes): 0 of 1Polyplex2/37Reliant Cellular0/19Stakes MFG0/15Reynolds Tobacco0/5Kalpataru3/3Bobrick VAAV1/1Bobrick (3)1/1Dynamic Defect Types (Stak0/1
EpicSegmentProgress iSub-tasks iUnassigned iEpic statusFlags
INTEL-359 Polyplex i 2/37 (5%) 143 28 To Do 2
INTEL-206 Reliant Cellular withheld quote that Lindsey said does not cover cost. [Source: _context/email-voltaire-reliant-timeflow-2026-09-10.md; estimates/certainty-mothership-sep-2026/_context/how-intelgic-actually-quotes.md:66-73]" data-tip="Cellular-manufacturing customer. No agreed scope or kickoff date. Two contested sizings exist: 379.9 story points at an unstated velocity, and 'four people for fifteen weeks' against a withheld quote that Lindsey said does not cover cost. [Source: _context/email-voltaire-reliant-timeflow-2026-09-10.md; estimates/certainty-mothership-sep-2026/_context/how-intelgic-actually-quotes.md:66-73]">i 0/19 (0%) 2 18 Backlog 21
INTEL-212 Stakes MFG withheld for the first system and withheld for seven, on 30/40/30 payment milestones (purchase order / shipment and pre-installation / post-installation commissioning). Current scope adds dynamic recipe and camera settings plus roughly 50 new error codes. [Source: estimates/certainty-mothership-sep-2026/_context/how-intelgic-actually-quotes.md:12,34-51; _context/day-2026-09-08.md:50]" data-tip="Manufacturing customer, quoted 18 Dec 2025 at withheld for the first system and withheld for seven, on 30/40/30 payment milestones (purchase order / shipment and pre-installation / post-installation commissioning). Current scope adds dynamic recipe and camera settings plus roughly 50 new error codes. [Source: estimates/certainty-mothership-sep-2026/_context/how-intelgic-actually-quotes.md:12,34-51; _context/day-2026-09-08.md:50]">i 0/15 (0%) 8 14 Backlog 24
INTEL-348 Reynolds Tobacco i 0/5 (0%) 5 To Do 1
INTEL-283 Kalpataru i 3/3 (100%) 5 Done
INTEL-43 Bobrick VAAV withheld billed over about eighteen months and unpaid. Nothing ships until that is settled; capability is built platform-first and delivered once paid. [Source: _context/day-2026-09-08.md:67-75]" data-tip="Bobrick VAAV. Paused on payment grounds, not cancelled — roughly withheld billed over about eighteen months and unpaid. Nothing ships until that is settled; capability is built platform-first and delivered once paid. [Source: _context/day-2026-09-08.md:67-75]">i 1/1 (100%) To Do
INTEL-346 Bobrick (3) i 1/1 (100%) Done
INTEL-296 Dynamic Defect Types (Stakes) i 0/1 (0%) To Do

POC i

IntelgicPOC: 0 of 1IntelgicPOC0/1
EpicSegmentProgress iSub-tasks iUnassigned iEpic statusFlags
INTEL-355 IntelgicPOC i 0/1 (0%) 4 To Do 1

Internal & ops i

Demo Setup: 1 of 1Demo Setup1/1
EpicSegmentProgress iSub-tasks iUnassigned iEpic statusFlags
INTEL-42 Demo Setup i 1/1 (100%) To Do

Unsegmented i

Under an epic not in the lane map: 18 of 302; No epic anywhere up the parent chain: 44 of 115Under an epic not in the l18/302No epic anywhere up the pa44/115
EpicSegmentProgress iSub-tasks iUnassigned iEpic statusFlags
Under an epic not in the lane map i 18/302 (6%) 6 5 16
No epic anywhere up the parent chain i 44/115 (38%) 2 26 40

Everyone with work on the board

Every assignee in the INTEL project at the snapshot, Intelgic and AppsTango alike, counted over all issues including sub-tasks. The reassignment detail further down covers the four AppsTango-side people only.

AssigneeIn progress Not startedDone
(nobody assigned)129032
taylor118020
Derek1938
Kunal Dutta141323
Nirupam Jana1039
Sriparna Biswas5610
Intelgic10
erikdon.p818
Erven.j1717
rajesh.m175
roddur.g162
pabitra.d3312
Rhitban Sarkar423
jhantu.d236
Madhusudan Mandal141
abhisek.k41
Biplab Bag316

People & reassignment

291 open items across 4 people, of which 7 are already past code — pushed to dev, in QA, or waiting on deployment. Every issue links to Jira and every PR to GitHub.

Taylor: Task pending 179, WIP 1, Pushed to dev 1; Derek: Task pending 90, WIP 1, PR pending 1, Pushed to dev 2; Erven: Task pending 3, PR pending 1, Pushed to dev 3, In QA 1; Erik: Task pending 6, PR pending 2TaylorTask pending: 179179WIP: 1Pushed to dev: 1181DerekTask pending: 9090WIP: 1PR pending: 1Pushed to dev: 294ErvenTask pending: 33PR pending: 11Pushed to dev: 33In QA: 118ErikTask pending: 66PR pending: 228Task pendingWIPPR pendingPushed to devIn QA

Taylor 181 open 1 near delivery

Issue What it is / where it came from StageCodeSegment Idle i
INTEL-3 [Taylor] Ongoing call review + staffing/estimate coordination (Aug 13 calls, t
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 32d
INTEL-22 [Taylor] Risk register + skills matrix consolidation from 1:1 data
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 32d
INTEL-25 [Taylor] OPS-E7: Team Jira training sessions (two time zones) + dashboards v1
Not recorded on the ticket
Task pending
To Do
no PR found No epic anywhere up the parent chain i 32d
INTEL-553 [M9-B9] Give each environment its own deployment role
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-561 [M3-B1] Add the license_hosts table
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-562 [M3-B2] Create a licence host record when a seat is claimed
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-563 [M3-B3] Delete a licence host by revoking it
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-564 [M3-B4] List licence hosts on a licence
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-565 [M3-B5] Edit licence host records during seat reconciliation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-566 [M3-B6] Return a signed entitlement at activation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-567 [M3-B7] Stamp customer_id onto Core operational records
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-568 [M3-B8] Gate features on the entitlement claim
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-569 [M3-F1] Show licence and entitlement state in the client
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-570 [M3-B9] Run Core as an operating-system service
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-571 [M3-B10] Document the Entitlement Service API contract
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-572 [M3-TL1] Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-573 [M3-LA1] Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-574 [M3-T1] Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-575 [M3-RT1] Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-576 [M3-R1] Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-628 Terminate TLS on the Core API
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-629 Terminate TLS on the client web host
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-630 Issue client certificates at device pairing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-631 Client trusts and presents the Core certificate
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-632 Scope Android cleartext to the plant range
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-633 Add the iOS ATS configuration
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-634 Escrow the SQLCipher key at activation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-635 Recover an escrowed key
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-636 Document key backup for sites that decline escrow
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-637 Restrict custom-step files to a controlled directory
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-638 Gate recipe-with-code authoring behind a permission
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-639 Verify recipe signatures before execution
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-640 Fix fail-open session expiry in the client
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-641 Repair token refresh in the licence portal
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-642 Stop trusting browser storage for identity and role
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-643 Provision the recipe verification key at activation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-644 Suggested: Put a WAF in front of the cloud entry point
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-645 Suggested: Alert on anomalous request patterns
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-646 Suggested: Move cloud credentials into AWS Secrets Manager
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-647 Suggested: Store plant credentials in the OS secret store
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-648 Suggested: Stop shipping an API key in the portal bundle
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-649 Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-650 Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-651 Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-652 Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-653 Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-654 QA — Dev (20% of dev hours) — M2 - Transport security, key escrow and the reci
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-655 QA — Acceptance (10% of dev hours) — M2 - Transport security, key escrow and t
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-656 PM — M2 - Transport security, key escrow and the recipe boundary
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-657 TPM / Meeting time — M2 - Transport security, key escrow and the recipe bounda
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-658 QA — Dev (20% of dev hours) — M3 - Tenant and entitlement
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-659 QA — Acceptance (10% of dev hours) — M3 - Tenant and entitlement
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-660 PM — M3 - Tenant and entitlement
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-661 TPM / Meeting time — M3 - Tenant and entitlement
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-663 Design the installation list and detail screens
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-664 Build the installation screen skeletons
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-665 Export Core system metrics
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-666 Send a plant heartbeat
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-667 Stand up central log and metric aggregation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-668 Add correlation ids across components
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-669 Scrub fault reports at the edge
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-670 Capture faults in Certainty Core .NET
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-671 Capture faults in the Core Python vision stack
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-672 Capture faults in the operator client
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-673 Capture faults in the backend and portal
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-674 Fingerprint and group faults before alerting
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-675 Configure the alert rules
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-676 Monitor licence API uptime and error rate
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-677 Write a runbook for every page-level alert
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-678 List every installation and its health
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-679 Show one installation in detail
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-680 Define field-defect intake
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-681 Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-682 Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-683 Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-684 Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-685 Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-686 QA — Dev (20% of dev hours) — M4 - Remote monitoring and fault reporting
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-687 QA — Acceptance (10% of dev hours) — M4 - Remote monitoring and fault reportin
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-688 PM — M4 - Remote monitoring and fault reporting
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-689 TPM / Meeting time — M4 - Remote monitoring and fault reporting
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-691 Capture changes into an outbox
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-692 Drain the outbox to the cloud
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-693 Delete only what ingestion has acknowledged
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-694 Apply backpressure at the outbox high-water mark
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-695 Measure and alert on sync lag
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-696 Accept ingestion at the gateway
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-697 Provision one customer analytics database
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-698 Reject unattributed records
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-699 Read one metric back in the portal
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-700 Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-701 Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-702 Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-703 Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-704 Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-705 QA — Dev (20% of dev hours) — M5 - Outbox, retention and the thin vertical sli
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-706 QA — Acceptance (10% of dev hours) — M5 - Outbox, retention and the thin verti
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-707 PM — M5 - Outbox, retention and the thin vertical slice
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-708 TPM / Meeting time — M5 - Outbox, retention and the thin vertical slice
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-710 Design the analytics dashboards
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-711 Build the analytics screen skeletons
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-712 Ingest at production volume
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-713 Provision a customer analytics database automatically
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-714 Enforce retention per subscription plan
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-715 Migrate schema across every customer database
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-716 Serve inspection throughput reporting
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-717 Serve defect-rate reporting
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-718 Show the analytics overview
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-719 Show a site analytics report
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-720 Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-721 Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-722 Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-723 Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-724 Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-725 QA — Dev (20% of dev hours) — M6 - Analytics service
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-726 QA — Acceptance (10% of dev hours) — M6 - Analytics service
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-727 PM — M6 - Analytics service
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-728 TPM / Meeting time — M6 - Analytics service
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-730 Design the assistant panel
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-731 Build the assistant panel skeleton
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-732 Queue commands for a plant to collect
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-733 Execute read-only diagnostics on the plant
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-734 Execute bounded write commands on the plant
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-735 Gate every capability on recorded customer consent
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-736 Audit every command end to end
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-737 Show and control remote access in the portal
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-738 Expose the chat endpoints to paired clients
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-739 Use the assistant from the client
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-740 Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-741 Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-742 Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-743 Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-744 Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-745 QA — Dev (20% of dev hours) — M7 - Reaching inward: remote command and local A
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-746 QA — Acceptance (10% of dev hours) — M7 - Reaching inward: remote command and
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-747 PM — M7 - Reaching inward: remote command and local AI access
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-748 TPM / Meeting time — M7 - Reaching inward: remote command and local AI access
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-750 Select and stand up the identity provider
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-751 Validate provider tokens in Core
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-752 Validate provider tokens in the licence backend
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-753 Authenticate the operator client through the provider
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-754 Authenticate the portal through the provider
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-755 Migrate existing users to the provider
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-756 Retire the bespoke token endpoints
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-757 Give machine callers their own identity
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-758 Scope and audit what machine callers may do
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-759 Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-760 Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-761 Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-762 Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-763 Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-764 QA — Dev (20% of dev hours) — M8 - Identity standardisation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-765 QA — Acceptance (10% of dev hours) — M8 - Identity standardisation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-766 PM — M8 - Identity standardisation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-767 TPM / Meeting time — M8 - Identity standardisation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-791 Design the cloud admin surfaces
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-792 Build the cloud admin screen skeletons
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-793 Resolve the tenant on every admin request
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-794 Create a client
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-795 Read a client
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-796 List clients with pagination
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-797 Update a client
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-798 Deactivate a client and keep their history
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-799 Serve users scoped to their client
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-800 Record a payment against a client
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-801 Read payment status across monthly and yearly payers
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-802 Show payment status in the admin panel
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-803 Point the admin dashboards at the cloud API
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-804 Choose the inference backend, local by default
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-805 Add Bedrock as a selectable fallback
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-806 Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-807 Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-808 Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-809 Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-810 Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-811 QA — Dev (20% of dev hours) — M10 - Cloud control plane: admin, tenancy and pa
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-812 QA — Acceptance (10% of dev hours) — M10 - Cloud control plane: admin, tenancy
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-813 PM — M10 - Cloud control plane: admin, tenancy and payment status
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-814 TPM / Meeting time — M10 - Cloud control plane: admin, tenancy and payment sta
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-23 [Taylor] LEG-E8: Support contributor register + IP assignment tracking (coordi
Not recorded on the ticket
WIP
In Progress
no PR found No epic anywhere up the parent chain i 5d
INTEL-155 Engineering OS cold-start is not executable -- START_HERE.md steps 2 to 7 refe medium
Raised by the followup-2026-08-24 code audit
Pushed to dev
To Do
certainty-core#66merged Under an epic not in the lane map i 23d

Derek 94 open 2 near delivery

Issue What it is / where it came from StageCodeSegment Idle i
INTEL-9 QA-E6: Draft staging environment requirements + regression suite architecture
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 32d
INTEL-10 CERT-E5: Review decisioning-path test coverage gaps against the example repo C
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 32d
INTEL-27 Initial exploratory pass + first real PR reviews once real GitHub code access
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 32d
INTEL-156 Admin dashboards render hardcoded sample data with nothing in the UI to say so medium
Raised by the followup-2026-08-24 code audit
Task pending
To Do
no PR found Certainty Client 23d
INTEL-163 [Derek] Derek-Admin: Meetings, coordination, and time reconciliation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 21d
INTEL-190 flutter analyze error on certainty-client is invisible on dev because the qual
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 18d
INTEL-544 [M9-B1] Create the four-account organisation
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-545 [M9-B2] Apply the baseline guardrails
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-546 [M9-B3] Centralise the audit trail in shared services
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-547 [M9-B4] Stand up the identity source and federate it
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-548 [M9-B5a] Define the permission sets
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-549 [M9-B5b] Scope iam:PassRole to the platform path
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-550 [M9-B6] Make the console legible on sign-in
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-551 [M9-B7] Withdraw standing administrator access
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-552 [M9-B8] Express the whole topology as Terraform
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-554 [M9-B10] Write the migration runbook to the Intelgic account
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-555 [M9-TL1] Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-556 [M9-LA1] Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-557 [M9-T1] Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-558 [M9-RT1] Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-559 [M9-R1] Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-579 Wire CI in certainty-core
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-580 Wire CI in certainty-license-backend
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-581 Wire CI in certainty-client
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-582 Wire CI in certainty-license
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-583 Pin the .NET toolchain and lock NuGet restore
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-584 Pin the Python toolchain for the licence backend
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-585 Pin the Flutter SDK in both Flutter repositories
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-586 Add analysis_options.yaml to the licence portal
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-587 Apply branch protection across the repositories
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-588 Configure the production approval environment
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-589 Populate CODEOWNERS and PR templates
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-590 Suggested: Stand up a Linux CI runner
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-591 Suggested: Triage the platform-compatibility warnings
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-592 Suggested: Replace Windows-only imaging calls on shared paths
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-593 Suggested: Prove the Linux installer on a clean host
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-594 Suggested: Define the non-functional targets
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-595 Suggested: Make the targets measurable
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-596 Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-597 Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-598 Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-599 Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-600 Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-601 QA — Dev (20% of dev hours) — M0 - CI, gating and reproducibility
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-602 QA — Acceptance (10% of dev hours) — M0 - CI, gating and reproducibility
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-603 PM — M0 - CI, gating and reproducibility
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-604 TPM / Meeting time — M0 - CI, gating and reproducibility
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-606 Fix the licence portal build error
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-607 Add the ownership check to the customer licences endpoint
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-608 Rotate the exposed plant credentials
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-609 Repair the certainty-client analyze and test failures
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-610 Add the mock seam to the portal providers
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-611 Repair the licence portal test suite
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-612 Add a test suite to the licence backend
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-613 Move the licence backend onto gunicorn
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-614 Patch the high-severity dependency CVEs
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-615 Bind the licence backend rate limiter
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-616 Rate limit the public licence endpoints
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-617 Replace the Android debug keystore
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-618 Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-619 Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-620 Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-621 Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-622 Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-623 QA — Dev (20% of dev hours) — M1 - Critical remediation and distribution unblo
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-624 QA — Acceptance (10% of dev hours) — M1 - Critical remediation and distributio
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-625 PM — M1 - Critical remediation and distribution unblock
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-626 TPM / Meeting time — M1 - Critical remediation and distribution unblock
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-769 Build a Core installer that preserves the database key
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-770 Provide an update channel for plant servers
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-771 Submit the operator client to the stores
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-772 Build and ship the client web bundle from source
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-773 Deploy the portal automatically
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-774 Separate model updates from application updates
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-775 Rehearse promotion and rollback
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-776 Write the production runbooks
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-777 Toast and Log
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-778 Log and Alerts
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-779 Set Up Automated (Lint) Tests
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-780 Regression and unit testing
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-781 Build and Release
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-782 QA — Dev (20% of dev hours) — REL - Release and distribution
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-783 QA — Acceptance (10% of dev hours) — REL - Release and distribution
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-784 PM — REL - Release and distribution
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-785 TPM / Meeting time — REL - Release and distribution
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-786 QA — Dev (20% of dev hours) — M9 - AWS account topology and federated access
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-787 QA — Acceptance (10% of dev hours) — M9 - AWS account topology and federated a
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-788 PM — M9 - AWS account topology and federated access
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-789 TPM / Meeting time — M9 - AWS account topology and federated access
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 1d
INTEL-836 [M9-B11] Build the network layer modules/database requires
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 0d
INTEL-8 Draft QA test plan/checklist against the example repo structure
Not recorded on the ticket
WIP
In Progress
no PR found Under an epic not in the lane map i 22d
INTEL-29 CERT-E5: First test-coverage pass on decisioning path
Not recorded on the ticket
PR pending
To Do
certainty-client#36open Under an epic not in the lane map i 32d
INTEL-28 QA-E6: Regression suite v1 build-out against real Certainty code
Not recorded on the ticket
Pushed to dev
To Do
certainty-client#27merged certainty-license#33merged certainty-license#32closed certainty-license-backend#31merged certainty-core#30merged Under an epic not in the lane map i 32d
INTEL-113 Test coverage 28.49%, concentrated not targeted; suite requires a live plant L medium
Raised by the 2026-08-19 code audit
Pushed to dev
To Do
certainty-client#22merged Certainty Client 28d

Erven 8 open 4 near delivery

Issue What it is / where it came from StageCodeSegment Idle i
INTEL-17 Draft Python code-review standards + checklist (using the example BE repo's ci
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 32d
INTEL-35 CERT-E5: Expand Python test coverage on decisioning path
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 32d
INTEL-153 About 152MB of vendor SDK binaries committed to git medium
Raised by the 2026-08-21 code audit
Task pending
To Do
no PR found Certainty Core 25d
INTEL-114 Two live UI defects: stale values submitted silently, and an orphaned reinstal medium
Raised by the 2026-08-19 code audit
PR pending
To Do
certainty-client#21open Certainty Client 28d
INTEL-149 174 build warnings, including 132 platform-compatibility warnings against a sh medium
Raised by the 2026-08-21 code audit
Pushed to dev
To Do
certainty-core#23merged Certainty Core 25d
INTEL-151 No Python lint configuration exists, so there is no agreed standard to measure medium
Raised by the 2026-08-21 code audit
Pushed to dev
To Do
certainty-core#18merged Certainty Core 25d
INTEL-125 No CI, no analysis_options.yaml, and bin/eh does not exist medium
Raised by the 2026-08-19 code audit
Pushed to dev
To Do
certainty-license#17merged Certainty Web 5d
INTEL-141 Two parallel config systems that validate production secrets differently; one medium
Raised by the 2026-08-20 code audit
In QA
QA
certainty-license-backend#17merged Certainty Web 22d

Erik 8 open

Issue What it is / where it came from StageCodeSegment Idle i
INTEL-12 QA oversight framework + checklist setup (check on our side per Russ's note)
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 32d
INTEL-14 INF-E1: Define CI secret-scanning policy + pre-commit hook spec for the exampl
Not recorded on the ticket
Task pending
To Do
no PR found Under an epic not in the lane map i 32d
INTEL-15 QA-E6: Draft HIL (hardware-in-the-loop) bench requirements outline (with Rajes
Not recorded on the ticket
Task pending
Blocked
no PR found Under an epic not in the lane map i 1d
INTEL-30 AWS access monitoring + pipeline-failure alerting setup (ties to Rajesh's expl
Not recorded on the ticket
Task pending
Blocked
no PR found Under an epic not in the lane map i 1d
INTEL-31 INF-E4: CI/CD pipeline monitoring dashboards + alert tuning
Not recorded on the ticket
Task pending
Blocked
no PR found Under an epic not in the lane map i 1d
INTEL-32 QA-E6: HIL bench procurement research (vendor/spec options)
Not recorded on the ticket
Task pending
Blocked
no PR found Under an epic not in the lane map i 1d
INTEL-143 Vision pipeline exec()s Python named by a recipe, and the comment calls it a s high
Raised by the 2026-08-21 code audit
PR pending
To Do
certainty-core#22open Certainty Core 25d
INTEL-154 Swagger unauthenticated when enabled, BOM breaks .gitattributes, orphaned test low
Raised by the 2026-08-21 code audit
PR pending
To Do
certainty-core#21open Certainty Core 25d

Weekly track

overall completion: W37 35, W38 240%50%100%W37: 35W38: 24W37W38
WeekFromProgress Flags iHighResolved i Not measured i
2026-W37 2026-09-07 125/354 (35%) 17947 1
2026-W38 2026-09-14 154/643 (24%) 20446 46

What the flags are i

The Flags column above is the total of these seven checks. Each is a rule, not an opinion: the rule is written out so a number can be argued with. The red part of each bar is the serious ones.

Nothing has happened to it: Serious 12, Worth a look 105; Past its own due date: Serious 2, Worth a look 24; Merged with no review: Serious 25; Nobody owns it: Serious 3, Worth a look 12; Edits with no movement: Worth a look 14; Branch never promoted: Serious 3, Worth a look 3; Belongs to no epic: Serious 1Nothing has happened to itSerious: 1212Worth a look: 105105117Past its own due dateSerious: 22Worth a look: 242426Merged with no reviewSerious: 252525Nobody owns itSerious: 33Worth a look: 121215Edits with no movementWorth a look: 141414Branch never promotedSerious: 33Worth a look: 336Belongs to no epicSerious: 111SeriousWorth a look
CheckThis week Serious
Nothing has happened to it
An open issue whose status has not changed in 14 days. Serious at 30. Measured from the status history, never the `updated` field, which any edit bumps.
11712
Past its own due date
The due date on the ticket is in the past and the ticket is still open. Only an eighth of this board carries a due date, so this check sees a fraction of the work and says so.
262
Merged with no review
A pull request that reached the default branch with no review by anyone other than its author.
2525
Nobody owns it
Open issues with no assignee, grouped by the part of the board they sit in. Serious once a group passes 25.
153
Edits with no movement
A day on which many issues were edited without any of them changing status. Recorded because it inflates any measure based on `updated`, which is why none of ours are.
14
Branch never promoted
Commits sitting on one branch that are not on the branch below it — dev ahead of staging, staging ahead of production. Serious past 25 commits.
63
Belongs to no epic
Open issues with no epic anywhere up their parent chain. They roll up to no customer and appear on no segment view.
11

A flag is a question, not a fault. Several of these will turn out to be deliberate — work parked on purpose, a branch nobody intends to promote — and once someone says so, it can be dismissed rather than carried. Full detail per flag, with ages and first-seen dates, is on the Findings tab.

Bugs, and whose they are

113 bugs on the board, 51 of them still open. 3 are attributable to a named customer; the rest are platform work or carry no epic.

Stakes MFG — 3 open

Lindsey Nichols, 2026-09-16: "the camera exposure is stakes. That's currently what they're working on." Corroborated in the 2026-09-16 standup by Kunal Dutta, explaining what dynamic exposure is for: "for the stakes imaging, so like we have multiple colors of shirts, right? Some are dark, some are bright ... sometimes the images get either over or under exposed."

TicketWhat is wrongStateWhoRaised
INTEL-362StopCameraAsync destroys a MindVision settings session before checking the camera is runningTo DoKunal Dutta2026-09-11
INTEL-856Bracket rungs save frames taken at the wrong exposure — the MindVision exposure header is not frTo Donobody2026-09-16
INTEL-857An unsettled bracket rung is saved anyway, and its sidecar metadata hides the failureTo Donobody2026-09-16

Platform, not one customer’s — 16 open

These sit under Certainty Core, Web or Client. They affect whoever uses that part, which is usually everybody, so they are not counted against any single customer.

TicketWhat is wrongStateWhoRaised
INTEL-107develop fails flutter analyze and 2 tests; broken import hides 9 test casesTestingNirupam Jana2026-08-19
INTEL-108Release builds signed with the public Android debug keystore -- blocks distributionTestingNirupam Jana2026-08-19
INTEL-110Web builds store the JWT and device clientSecret in plaintext localStorageTestingNirupam Jana2026-08-19
INTEL-113Test coverage 28.49%, concentrated not targeted; suite requires a live plant LANTo DoDerek2026-08-19
INTEL-114Two live UI defects: stale values submitted silently, and an orphaned reinstall pathTo DoErven.j2026-08-19
INTEL-125No CI, no analysis_options.yaml, and bin/eh does not existTo DoErven.j2026-08-19
INTEL-141Two parallel config systems that validate production secrets differently; one uses assertQAErven.j2026-08-20
INTEL-143Vision pipeline exec()s Python named by a recipe, and the comment calls it a sandboxTo Doerikdon.p2026-08-21
INTEL-149174 build warnings, including 132 platform-compatibility warnings against a shipped Linux SDKTo DoErven.j2026-08-21
INTEL-151No Python lint configuration exists, so there is no agreed standard to measure againstTo DoErven.j2026-08-21
INTEL-153About 152MB of vendor SDK binaries committed to gitTo DoErven.j2026-08-21
INTEL-154Swagger unauthenticated when enabled, BOM breaks .gitattributes, orphaned test project, deprecatTo Doerikdon.p2026-08-21
INTEL-156Admin dashboards render hardcoded sample data with nothing in the UI to say so -- Super Admin, STo DoDerek2026-08-24
INTEL-284Release builds ship chat/ and voice/ Python as source instead of .pycPush to DevKunal Dutta2026-09-07
INTEL-535Recover the orphaned certainty-client audit-remediation work onto devTo Donobody2026-09-11
INTEL-59[kunald-intelgic] MindVision Camera: Custom ROI Draw IssuePush to DevKunal Dutta2026-08-18

Under no epic at all — 32 open

Nothing on the ticket says which part of the product or which customer these belong to. They are in nobody’s total, which is the strongest argument on this page for giving every ticket an epic.

TicketWhat is wrongStateWhoRaised
INTEL-155Engineering OS cold-start is not executable -- START_HERE.md steps 2 to 7 reference trees that dTo Dotaylor2026-08-24
INTEL-162Developer-machine absolute paths committed in build files (certainty-client + certainty-core) - To Donobody2026-08-25
INTEL-164Recipe dropdowns offer five spellings of the same two concepts, and the default one fails the onTo Donobody2026-08-27
INTEL-165In-built tool panel_inspection resolves a module that is not in the repository, so it fails on uTo Donobody2026-08-27
INTEL-190flutter analyze error on certainty-client is invisible on dev because the quality gate skips anaTo DoDerek2026-08-28
INTEL-260Creating a user with a soft-deleted username returns 500Push to DevKunal Dutta2026-09-04
INTEL-261Username uniqueness is case-sensitive on SQLite and case-insensitive on SQL ServerPush to DevKunal Dutta2026-09-04
INTEL-262installer/ is gitignored — Windows and Linux installer sources are untrackedPush to DevKunal Dutta2026-09-04
INTEL-273Capture run releases the robot claim before the return-home motion finishesTo Doroddur.g2026-09-04
INTEL-274Failed approach leaves stale `previous`, defeating the safe-Z retract guardTo Doroddur.g2026-09-04
INTEL-275Capture endpoints that move the robot require authentication but no permissionTo Doroddur.g2026-09-04
INTEL-276Capture endpoints return raw exception messages in 500 response bodiesTo Doroddur.g2026-09-04
INTEL-277ROS distro auto-discovery picks /opt/ros/rolling over the installed releaseTo Doroddur.g2026-09-04
INTEL-278robot_model is not checked against the recipe allowlist, and five of six robot models ship withoTo Doroddur.g2026-09-04
INTEL-282Fix cross-tenant license listing for customer-less accountsTestingnobody2026-09-07
INTEL-322Migration 032 recovery path omits the transaction argument and throws instead of recoveringTo Donobody2026-09-09
INTEL-323A failed login leaves the PREVIOUS user still authenticatedTo Donobody2026-09-09
INTEL-324A password change that SUCCEEDED is reported as failed, locking the user outTo Donobody2026-09-09
INTEL-325Discarding one capture also removes any capture whose name it prefixes (cap-1 takes cap-10)To Donobody2026-09-09
INTEL-326WebSocket error classifier reads digits from the address as an HTTP status, misdiagnosing networTo Donobody2026-09-09
INTEL-327A ticket failure on the camera slot path forecloses the camera-id fallback entirelyTo Donobody2026-09-09
INTEL-328create_admin.py provisions admin accounts below the project's own password policyTo Donobody2026-09-09
INTEL-329Model-path allowlist bypass exists at two sites; production reaches bothTo DoKunal Dutta2026-09-09
INTEL-330The Success flag on an inference result is structurally incapable of being falseTo Donobody2026-09-09
INTEL-331Two TLS tests have an undeclared external prerequisite and fail on any clean checkoutTo Donobody2026-09-09
INTEL-332A TLS test passes for the wrong reason and cannot distinguish a working port from an absent oneTo Donobody2026-09-09
INTEL-333torch is not pinned - every torch line in requirements.txt is commented outTo Donobody2026-09-09
INTEL-836[M9-B11] Build the network layer modules/database requiresTo DoDerek2026-09-15
INTEL-853ReadSidecar reports a capture as untagged during the sidecar replace windowTo Donobody2026-09-16
INTEL-854/auth/login has no brute-force ceiling now that the limiter is partitioned per callerTo Donobody2026-09-16
INTEL-855Refresh tokens are never issued, so POST /auth/refresh can only ever return 401To Donobody2026-09-16
INTEL-865Imaging bounding boxes: Pan/Draw/Edit tool selector with zoom-aware drawing and resize handlesIn ProgressNirupam Jana2026-09-16

Every issue whose Jira type is Bug, read from the same snapshot as the rest of this page. Done and dropped bugs are excluded from the counts above; 62 of them are closed. Attribution rules and their sources: weekly/engagements.py.

Findings from the automated checks

204 things seven rules noticed when they last ran over Jira and GitHub. A finding is a question to answer, not work that has stopped.

Divided by section. “First seen” comes from the flag ledger, so each finding carries its own history: something raised three weeks ago and still true reads differently from something raised today. Resolved items are reported once and then dropped, so a recurrence shows as new. What each rule looks for is on .

No epic anywhere up the parent chain 40

SeverityFindingFirst seen iAgeState i
high INTEL-25 — [Taylor] OPS-E7: Team Jira training sessions (two time zones) + dashbo
32d since the status last changed (now To Do, taylor)
2026-09-11 5d standing open
high No epic anywhere up the parent chain: 26 open issues with no assignee
e.g. INTEL-37, INTEL-162, INTEL-164, INTEL-165, INTEL-187, INTEL-188…
2026-09-11 5d standing
medium INTEL-37 — [RETIRED] TQ Admin -- merged into INTEL-36 and the [Taylor] stories
27d since the status last changed (now Removed, unassigned)
2026-09-11 5d standing open
medium INTEL-71 — [sriparnab-intelgic] Auto Clear Implementation
29d since the status last changed (now Testing, Sriparna Biswas)
2026-09-11 5d standing open
medium INTEL-162 — Developer-machine absolute paths committed in build files (certainty-c
22d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-164 — Recipe dropdowns offer five spellings of the same two concepts, and th
20d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-165 — In-built tool panel_inspection resolves a module that is not in the re
20d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-166 — Present the project onboarding and management process
19d since the status last changed (now To Do, Intelgic)
2026-09-11 5d standing open
medium INTEL-167 — Give an ETA for remote access to a test environment
19d since the status last changed (now To Do, Intelgic)
2026-09-11 5d standing open
medium INTEL-168 — Talk to Biplab about the Bobrick missing-feature email
19d since the status last changed (now To Do, Intelgic)
2026-09-11 5d standing open
medium INTEL-169 — Enable Copilot at GitHub Enterprise level
19d since the status last changed (now To Do, Intelgic)
2026-09-11 5d standing open
medium INTEL-170 — Walk Taylor through the architecture and hardware chain
19d since the status last changed (now To Do, Intelgic)
2026-09-11 5d standing open
medium INTEL-171 — Supply the list of actions that must be audited
19d since the status last changed (now To Do, Intelgic)
2026-09-11 5d standing open
medium INTEL-172 — Decide whether the plant LAN is treated as trusted
19d since the status last changed (now To Do, Intelgic)
2026-09-11 5d standing open
medium INTEL-173 — Set the retention window and the outage behaviour
19d since the status last changed (now To Do, Intelgic)
2026-09-11 5d standing open
medium INTEL-174 — Decide what the cloud AI layer is for
19d since the status last changed (now To Do, Intelgic)
2026-09-11 5d standing open
medium INTEL-175 — Review the INTEL-149 PR and report an ETA
19d since the status last changed (now To Do, Kunal Dutta)
2026-09-11 5d standing open
medium INTEL-176 — Push a fresh working Flutter web build
19d since the status last changed (now To Do, Kunal Dutta)
2026-09-11 5d standing open
medium INTEL-178 — Confirm the WoodenPanel and cutlist files can be removed
19d since the status last changed (now To Do, Kunal Dutta)
2026-09-11 5d standing open
medium INTEL-179 — Give a date for the roles and permissions rework
19d since the status last changed (now To Do, Kunal Dutta)
2026-09-11 5d standing open
medium INTEL-180 — Update PR status and re-review INTEL-144
19d since the status last changed (now To Do, rajesh.m)
2026-09-11 5d standing open
medium INTEL-181 — Scoping docs for conformance items 7 to 11
19d since the status last changed (now To Do, rajesh.m)
2026-09-11 5d standing open
medium INTEL-182 — Set up the POC repository and branch structure
19d since the status last changed (now To Do, rajesh.m)
2026-09-11 5d standing open
medium INTEL-184 — Verify the Python library licences and their imports
19d since the status last changed (now To Do, Sriparna Biswas)
2026-09-11 5d standing open
medium INTEL-185 — Review the open PRs on certainty-client
19d since the status last changed (now To Do, Nirupam Jana)
2026-09-11 5d standing open
medium INTEL-186 — Validate the sandbox around client-written Python in recipes
19d since the status last changed (now To Do, Kunal Dutta)
2026-09-11 5d standing open
medium INTEL-187 — Reconcile certainty-client after the 26 August force-push
19d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-188 — Rename the Swagger / loopback ticket as a post-backend item
19d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-247 — Add inspection report tracking — and surface a summary on `/site-admin
due 2026-09-09, 7d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-248 — Send the client list (company to contact) and the POC mapping
due 2026-09-04, 12d late, status To Do
2026-09-11 5d standing open
medium INTEL-249 — Send the Bobrick SOP monitoring document (UI and workflow)
due 2026-09-04, 12d late, status In Progress
2026-09-11 5d standing open
medium INTEL-250 — Comment on and move the cards for the licence PRs in both repositories
due 2026-09-04, 12d late, status To Do
2026-09-11 5d standing open
medium INTEL-252 — Install the SSL certificate on the Stakes deployment
due 2026-09-05, 11d late, status To Do
2026-09-11 5d standing open
medium INTEL-254 — Send the current email addresses for Madhusudan and Abhishek cloud acc
due 2026-09-04, 12d late, status To Do
2026-09-11 5d standing open
medium INTEL-260 — Creating a user with a soft-deleted username returns 500
due 2026-09-04, 12d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-261 — Username uniqueness is case-sensitive on SQLite and case-insensitive o
due 2026-09-09, 7d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-262 — installer/ is gitignored — Windows and Linux installer sources are unt
due 2026-09-04, 12d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-291 — Retire MindVisionSdk.cs — consolidate MindVision camera SDK onto the M
due 2026-09-09, 7d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-315 — Add plant timezone configuration: ServerSettings key, admin API, and c
due 2026-09-09, 7d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-237 — Test story
14d since the status last changed (now Removed, unassigned)
2026-09-16 0d new open

Engineering process 31

SeverityFindingFirst seen iAgeState i
high certainty-client #33 merged with no review
"Pull release note, version correction, sop feature" into dev, merged 2026-09-07 by sriparnab-intelgic
2026-09-11 5d standing open
high certainty-license #36 merged with no review
"close two gaps a follow-up review found" into dev, merged 2026-09-07 by sriparnab-intelgic
2026-09-11 5d standing open
high certainty-license-backend #39 merged with no review
"test(backend): pin three QA findings — revocation scope, exp" into dev, merged 2026-09-11 by derek422
2026-09-11 5d standing open
high certainty-license-backend #38 merged with no review
"fix(backend): five plan/customer route and service defects f" into dev, merged 2026-09-11 by derek422
2026-09-11 5d standing open
high certainty-license-backend #37 merged with no review
"INTEL-282: licence scoping boundaries, and a decorator that " into dev, merged 2026-09-10 by derek422
2026-09-11 5d standing open
high certainty-license-backend #36 merged with no review
"Test coverage for plans and customers: 54 tests, 35/35 mutat" into dev, merged 2026-09-10 by derek422
2026-09-11 5d standing open
high certainty-license-backend #35 merged with no review
"Add v1.0.0 release notes" into dev, merged 2026-09-07 by sriparnab-intelgic
2026-09-11 5d standing open
high certainty-license-backend #34 merged with no review
"INTEL-282:Fix cross-tenant license listing for customer-less" into dev, merged 2026-09-07 by sriparnab-intelgic
2026-09-11 5d standing open
high certainty-license-backend #33 merged with no review
"INTEL-138: correct the CI lint comment to measured numbers (" into dev, merged 2026-09-07 by derek422
2026-09-11 5d standing open
high certainty-license-backend #32 merged with no review
"INTEL-189: exec gunicorn in run.sh so SIGTERM reaches it, an" into dev, merged 2026-09-07 by derek422
2026-09-11 5d standing open
high certainty-core #64 merged with no review
"INTEL-247: inspection report schema, dashboard read path, an" into dev, merged 2026-09-09 by kunald-intelgic
2026-09-11 5d standing open
high certainty-core #63 merged with no review
"INTEL-291: consolidate MindVision camera SDK onto a single b" into dev, merged 2026-09-09 by kunald-intelgic
2026-09-11 5d standing open
high certainty-core #62 merged with no review
"INTEL-261: make username uniqueness case-insensitive on both" into dev, merged 2026-09-09 by kunald-intelgic
2026-09-11 5d standing open
high certainty-core #61 merged with no review
"fix: byte-compile chat and voice Python in Release builds (I" into dev, merged 2026-09-07 by kunald-intelgic
2026-09-11 5d standing open
high certainty-core #59 merged with no review
"Add SOP Monitoring: instruction authoring, live run engine, " into dev, merged 2026-09-08 by BiplabB-Intelgic
2026-09-11 5d standing open
high certainty-license: dev is 66 commits ahead of staging
66 commits on dev are not on staging. This is a branch comparison, not a statement about any particular fix being live.
2026-09-11 5d standing
high certainty-license-backend: dev is 63 commits ahead of staging
63 commits on dev are not on staging. This is a branch comparison, not a statement about any particular fix being live.
2026-09-11 5d standing
high certainty-core: dev is 113 commits ahead of staging
113 commits on dev are not on staging. This is a branch comparison, not a statement about any particular fix being live.
2026-09-11 5d standing
high certainty-client #37 merged with no review
"Feature/andriod keystore" into feature/merge-release-25-09, merged 2026-09-14 by nirupamj-intelgic
2026-09-16 0d new open
high certainty-core #71 merged with no review
"INTEL-845 / INTEL-852: show the whole exposure ladder while " into merge/dev-2026-09-25, merged 2026-09-16 by kunald-intelgic
2026-09-16 0d new open
high certainty-core #69 merged with no review
"INTEL-536: exchange an SSO id_token for a Certainty token" into merge/dev-2026-09-25, merged 2026-09-16 by kunald-intelgic
2026-09-16 0d new open
high certainty-core #66 merged with no review
"INTEL-155: make START_HERE honest about the missing .certain" into dev, merged 2026-09-14 by TaylorQ-Intelgic
2026-09-16 0d new open
high ial-infrastructure #11 merged with no review
"M9-B5a: split BuildDeploy per environment, so the matrix gra" into main, merged 2026-09-16 by TaylorQ-Intelgic
2026-09-16 0d new open
high ial-infrastructure #9 merged with no review
"Run the mutation harness in CI, and un-stale the evidence PR" into main, merged 2026-09-16 by TaylorQ-Intelgic
2026-09-16 0d new open
high ial-infrastructure #6 merged with no review
"M9-B9: separate the deploy roles by claim, and let product r" into main, merged 2026-09-16 by TaylorQ-Intelgic
2026-09-16 0d new open
high ial-infrastructure #4 merged with no review
"M9-B5a: make people able to log in, and stop trusting the st" into main, merged 2026-09-16 by TaylorQ-Intelgic
2026-09-16 0d new open
high ial-infrastructure #3 merged with no review
"fix(M9-B2): do not exempt Identity Center from the region SC" into main, merged 2026-09-15 by TaylorQ-Intelgic
2026-09-16 0d new open
high ial-infrastructure #2 merged with no review
"fix(M9): close review items 1, 3 and 5 — and correct an OIDC" into m9/aws-accounts-federated-access, merged 2026-09-15 by TaylorQ-Intelgic
2026-09-16 0d new open
medium ial-program-docs: dev is 9 commits ahead of staging
9 commits on dev are not on staging. This is a branch comparison, not a statement about any particular fix being live.
2026-09-11 5d standing
medium certainty-client: dev is 23 commits ahead of staging
23 commits on dev are not on staging. This is a branch comparison, not a statement about any particular fix being live.
2026-09-11 5d standing
medium ial-example-repo-be: dev is 2 commits ahead of staging
2 commits on dev are not on staging. This is a branch comparison, not a statement about any particular fix being live.
2026-09-16 0d new

Certainty Core 26

SeverityFindingFirst seen iAgeState i
high INTEL-269 — Client Management
due 2026-08-28, 19d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-45 — Data Saving and DQC Implementation
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-46 — Add raw-pixel payload format to CFIP inference transport (eliminate JP
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-47 — Human in Loop Inspection Workflow
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-49 — Extract and save input files for re-inspection
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-50 — Make Timestamp db as Historian
29d since the status last changed (now To Do, Kunal Dutta)
2026-09-11 5d standing open
medium INTEL-51 — Implement SCADA
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-52 — Unique Signature Implementation for User
29d since the status last changed (now To Do, Kunal Dutta)
2026-09-11 5d standing open
medium INTEL-53 — Trigger laser and display laser-3d-view in recipe setup screen
29d since the status last changed (now To Do, pabitra.d)
2026-09-11 5d standing open
medium INTEL-54 — [pabitra-intelgic] Back Button for Recipe Set up Screen
29d since the status last changed (now To Do, pabitra.d)
2026-09-11 5d standing open
medium INTEL-58 — [kunald-intelgic] OPC UA Implementation
29d since the status last changed (now To Do, Kunal Dutta)
2026-09-11 5d standing open
medium INTEL-143 — Vision pipeline exec()s Python named by a recipe, and the comment call
25d since the status last changed (now To Do, erikdon.p)
2026-09-11 5d standing open
medium INTEL-149 — 174 build warnings, including 132 platform-compatibility warnings agai
25d since the status last changed (now To Do, Erven.j)
2026-09-11 5d standing open
medium INTEL-151 — No Python lint configuration exists, so there is no agreed standard to
25d since the status last changed (now To Do, Erven.j)
2026-09-11 5d standing open
medium INTEL-153 — About 152MB of vendor SDK binaries committed to git
25d since the status last changed (now To Do, Erven.j)
2026-09-11 5d standing open
medium INTEL-154 — Swagger unauthenticated when enabled, BOM breaks .gitattributes, orpha
25d since the status last changed (now To Do, erikdon.p)
2026-09-11 5d standing open
medium Certainty Core: 5 open issues with no assignee
e.g. INTEL-45, INTEL-46, INTEL-47, INTEL-49, INTEL-51
2026-09-11 5d standing
medium INTEL-66 — [BiplabB-Intelgic] SOP - Dynamic work instruction setup and Runtime In
due 2026-09-03, 13d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-244 — Activity Log
due 2026-09-03, 13d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-259 — Hardware Management
due 2026-09-04, 12d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-284 — Release builds ship chat/ and voice/ Python as source instead of .pyc
due 2026-09-08, 8d late, status Push to Dev
2026-09-11 5d standing open
medium INTEL-59 — [kunald-intelgic] MindVision Camera: Custom ROI Draw Issue
14d since the status last changed (now Push to Dev, Kunal Dutta)
2026-09-16 0d new open
medium INTEL-68 — [kunald-intelgic] MindVision Camera; Alternatively use Config Profiles
14d since the status last changed (now Push to Dev, Kunal Dutta)
2026-09-16 0d new open
medium INTEL-69 — [kunald-intelgic] WebSocket JWT URL Exposure - Short-lived Ticket Exch
14d since the status last changed (now Push to Dev, Kunal Dutta)
2026-09-16 0d new open
medium INTEL-72 — [kunald-intelgic] Role Based Permission System
14d since the status last changed (now To Do, Kunal Dutta)
2026-09-16 0d new open
medium INTEL-73 — [kunald-intelgic] Super Admin Dashboard API: Server Stats and Workstat
14d since the status last changed (now Push to Dev, Kunal Dutta)
2026-09-16 0d new open

Stakes MFG 24

SeverityFindingFirst seen iAgeState i
medium Stakes MFG: 22 open issues with no assignee
e.g. INTEL-213, INTEL-215, INTEL-216, INTEL-217, INTEL-218, INTEL-219…
2026-09-11 5d standing
medium INTEL-213 — AI Model Training
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-214 — Data Annotation
15d since the status last changed (now Backlog, Madhusudan Mandal)
2026-09-16 0d new open
medium INTEL-215 — Training
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-216 — Validation and Fine Tuning
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-217 — Vision AI Software and Defect Detection Run Time Screen
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-218 — Design
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-219 — Backend Python
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-220 — Certainty Core API
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-221 — Barcode Reference Image-Local storage/Stakes API
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-222 — Configure print image confirmation logic
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-223 — Configure coordinate verification logic
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-224 — Configure garment color confirmation logic
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-225 — Configure hologram label presence & positional validation Quality D
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-226 — Banding
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-227 — Registration errors
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-228 — Blur
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-229 — Each defect category will support a strictness score ranging from 0.0
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-230 — Rest API Expose
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-231 — Required data send from python backend to core
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-232 — Core to push the result to Stakes API
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-233 — QA
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-234 — Project Management
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-235 — Planning & Design
14d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open

Reliant Cellular 21

SeverityFindingFirst seen iAgeState i
medium Reliant Cellular: 18 open issues with no assignee
e.g. INTEL-191, INTEL-192, INTEL-193, INTEL-194, INTEL-195, INTEL-196…
2026-09-11 5d standing
medium INTEL-191 — Template Imaging Screen
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-192 — Template Backend Screen
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-193 — Runtime Screen Design
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-194 — Runtime Backend
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-195 — Imaging for AI Model Training
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-196 — Annotation Validation
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-197 — Training
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-198 — Fine Tuning
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-199 — Dashboard Design
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-200 — Logic Building
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-201 — Database
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-202 — QA Testing
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-203 — Planning & Design
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-204 — Project Management
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-207 — Imaging Screen
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-208 — Runtime Screen
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-209 — AI Model Training
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-342 — UI/UX Design
due 2026-09-15, 1d late, status Push to Dev
2026-09-16 0d new open
medium INTEL-343 — Receiving Station UI/UX
due 2026-09-15, 1d late, status Push to Dev
2026-09-16 0d new open
medium INTEL-344 — Shipping Station UI/UX
due 2026-09-15, 1d late, status Push to Dev
2026-09-16 0d new open

Under an epic not in the lane map 16

SeverityFindingFirst seen iAgeState i
high INTEL-3 — [Taylor] Ongoing call review + staffing/estimate coordination (Aug 13
32d since the status last changed (now To Do, taylor)
2026-09-11 5d standing open
high INTEL-9 — QA-E6: Draft staging environment requirements + regression suite archi
32d since the status last changed (now To Do, Derek)
2026-09-11 5d standing open
high INTEL-10 — CERT-E5: Review decisioning-path test coverage gaps against the exampl
32d since the status last changed (now To Do, Derek)
2026-09-11 5d standing open
high INTEL-12 — QA oversight framework + checklist setup (check on our side per Russ's
32d since the status last changed (now To Do, erikdon.p)
2026-09-11 5d standing open
high INTEL-14 — INF-E1: Define CI secret-scanning policy + pre-commit hook spec for th
32d since the status last changed (now To Do, erikdon.p)
2026-09-11 5d standing open
high INTEL-17 — Draft Python code-review standards + checklist (using the example BE r
32d since the status last changed (now To Do, Erven.j)
2026-09-11 5d standing open
high INTEL-22 — [Taylor] Risk register + skills matrix consolidation from 1:1 data
32d since the status last changed (now To Do, taylor)
2026-09-11 5d standing open
high INTEL-27 — Initial exploratory pass + first real PR reviews once real GitHub code
32d since the status last changed (now To Do, Derek)
2026-09-11 5d standing open
high INTEL-28 — QA-E6: Regression suite v1 build-out against real Certainty code
32d since the status last changed (now To Do, Derek)
2026-09-11 5d standing open
high INTEL-29 — CERT-E5: First test-coverage pass on decisioning path
32d since the status last changed (now To Do, Derek)
2026-09-11 5d standing open
high INTEL-35 — CERT-E5: Expand Python test coverage on decisioning path
32d since the status last changed (now To Do, Erven.j)
2026-09-11 5d standing open
medium INTEL-8 — Draft QA test plan/checklist against the example repo structure
22d since the status last changed (now In Progress, Derek)
2026-09-11 5d standing open
medium INTEL-155 — Engineering OS cold-start is not executable -- START_HERE.md steps 2 t
23d since the status last changed (now To Do, taylor)
2026-09-11 5d standing open
medium INTEL-163 — [Derek] Derek-Admin: Meetings, coordination, and time reconciliation
21d since the status last changed (now To Do, Derek)
2026-09-11 5d standing open
medium INTEL-190 — flutter analyze error on certainty-client is invisible on dev because
18d since the status last changed (now To Do, Derek)
2026-09-11 5d standing open
medium Under an epic not in the lane map: 11 open issues with no assignee
e.g. INTEL-815, INTEL-816, INTEL-817, INTEL-818, INTEL-819, INTEL-820…
2026-09-16 0d new

Board hygiene 14

SeverityFindingFirst seen iAgeState i
medium 2026-08-14: 35 issues edited, no status change
35 issues touched that day, 0 of them actually transitioned. Most edits by taylor (42).
2026-09-11 5d standing
medium 2026-08-17: 34 issues edited, no status change
34 issues touched that day, 0 of them actually transitioned. Most edits by taylor (34).
2026-09-11 5d standing
medium 2026-08-18: 22 issues edited, no status change
69 issues touched that day, 47 of them actually transitioned. Most edits by taylor (295).
2026-09-11 5d standing
medium 2026-08-19: 22 issues edited, no status change
23 issues touched that day, 1 of them actually transitioned. Most edits by taylor (46).
2026-09-11 5d standing
medium 2026-08-20: 59 issues edited, no status change
60 issues touched that day, 1 of them actually transitioned. Most edits by taylor (257), Erven.j (1).
2026-09-11 5d standing
medium 2026-08-21: 22 issues edited, no status change
23 issues touched that day, 1 of them actually transitioned. Most edits by taylor (78), Derek (3).
2026-09-11 5d standing
medium 2026-08-25: 48 issues edited, no status change
64 issues touched that day, 16 of them actually transitioned. Most edits by taylor (146), Derek (16).
2026-09-11 5d standing
medium 2026-09-01: 22 issues edited, no status change
47 issues touched that day, 25 of them actually transitioned. Most edits by Intelgic (99), taylor (22).
2026-09-11 5d standing
medium 2026-09-02: 61 issues edited, no status change
68 issues touched that day, 7 of them actually transitioned. Most edits by taylor (51), Derek (16).
2026-09-11 5d standing
medium 2026-09-04: 20 issues edited, no status change
60 issues touched that day, 40 of them actually transitioned. Most edits by Intelgic (134), Derek (39).
2026-09-11 5d standing
medium 2026-09-11: 166 issues edited, no status change
216 issues touched that day, 50 of them actually transitioned. Most edits by rajesh.m (130), taylor (36).
2026-09-11 5d standing
medium 2026-09-14: 130 issues edited, no status change
159 issues touched that day, 29 of them actually transitioned. Most edits by taylor (191), rajesh.m (26).
2026-09-16 0d new
medium 2026-09-15: 54 issues edited, no status change
69 issues touched that day, 15 of them actually transitioned. Most edits by devin (79), taylor (73).
2026-09-16 0d new
medium 2026-09-16: 21 issues edited, no status change
50 issues touched that day, 29 of them actually transitioned. Most edits by rajesh.m (30), Kunal Dutta (28).
2026-09-16 0d new

Unsegmented 11

SeverityFindingFirst seen iAgeState i
high Unsegmented: 29 open issues with no assignee
e.g. INTEL-38, INTEL-39, INTEL-40, INTEL-41, INTEL-42, INTEL-43…
2026-09-11 5d standing
high 363 open issues belong to no epic
These appear on no segment view and roll up to no customer or product line. e.g. INTEL-3, INTEL-8, INTEL-9, INTEL-10, INTEL-12, INTEL-14, INTEL-15, INTEL-17
2026-09-11 5d standing
medium INTEL-38 — Certainty Core
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-39 — Certainty Client
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-40 — Certainty Web
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-41 — Certainty User Manual
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-42 — Demo Setup
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-43 — Bobrick VAAV
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-345 — Bobrick
due 2026-09-11, 5d late, status To Do
2026-09-11 5d standing open
medium INTEL-206 — Reliant Cellular
16d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open
medium INTEL-212 — Stakes MFG
15d since the status last changed (now Backlog, unassigned)
2026-09-16 0d new open

Certainty Client 6

SeverityFindingFirst seen iAgeState i
high INTEL-67 — [sukhendu-intelgic] SOP- Analytics reports (Cloud)
due 2026-08-11, 36d late, status Removed
2026-09-11 5d standing open
medium INTEL-113 — Test coverage 28.49%, concentrated not targeted; suite requires a live
28d since the status last changed (now To Do, Derek)
2026-09-11 5d standing open
medium INTEL-114 — Two live UI defects: stale values submitted silently, and an orphaned
28d since the status last changed (now To Do, Erven.j)
2026-09-11 5d standing open
medium INTEL-156 — Admin dashboards render hardcoded sample data with nothing in the UI t
23d since the status last changed (now To Do, Derek)
2026-09-11 5d standing open
medium Certainty Client: 1 open issues with no assignee
e.g. INTEL-535
2026-09-11 5d standing
medium INTEL-110 — Web builds store the JWT and device clientSecret in plaintext localSto
16d since the status last changed (now Testing, Nirupam Jana)
2026-09-16 0d new open

SSO for Certainty Client 4

SeverityFindingFirst seen iAgeState i
medium INTEL-297 — Sign in to the Certainty Client with a single, unified identity
due 2026-09-10, 6d late, status Testing
2026-09-11 5d standing open
medium INTEL-298 — Configure an organization's own identity provider
due 2026-09-11, 5d late, status Testing
2026-09-11 5d standing open
medium INTEL-299 — End a session cleanly, everywhere it exists
due 2026-09-15, 1d late, status Testing
2026-09-16 0d new open
medium INTEL-536 — [Backend] Exchange an SSO id_token for a Certainty token (POST /auth/s
due 2026-09-15, 1d late, status Testing
2026-09-16 0d new open

Certainty Web 3

SeverityFindingFirst seen iAgeState i
medium INTEL-48 — Migration of Cretainty Core screens to web version (Cretainty Web)
29d since the status last changed (now To Do, unassigned)
2026-09-11 5d standing open
medium INTEL-141 — Two parallel config systems that validate production secrets different
22d since the status last changed (now QA, Erven.j)
2026-09-11 5d standing open
medium Certainty Web: 1 open issues with no assignee
e.g. INTEL-48
2026-09-11 5d standing

Polyplex 2

SeverityFindingFirst seen iAgeState i
high Polyplex: 155 open issues with no assignee
e.g. INTEL-363, INTEL-364, INTEL-365, INTEL-366, INTEL-367, INTEL-368…
2026-09-11 5d standing
medium INTEL-514 — Design multi-camera imaging screen layout (grid/tile view for all came
due 2026-09-14, 2d late, status Testing
2026-09-16 0d new open

Role-Based User Management 1

SeverityFindingFirst seen iAgeState i
medium Role-Based User Management: 11 open issues with no assignee
e.g. INTEL-301, INTEL-302, INTEL-303, INTEL-304, INTEL-504, INTEL-505…
2026-09-11 5d standing

Reynolds Tobacco 1

SeverityFindingFirst seen iAgeState i
medium Reynolds Tobacco: 5 open issues with no assignee
e.g. INTEL-349, INTEL-350, INTEL-351, INTEL-352, INTEL-353
2026-09-11 5d standing

API Gateway Layer 1

SeverityFindingFirst seen iAgeState i
medium API Gateway Layer: 3 open issues with no assignee
e.g. INTEL-305, INTEL-306, INTEL-307
2026-09-11 5d standing

Dynamic Camera Exposure 1

SeverityFindingFirst seen iAgeState i
medium Dynamic Camera Exposure: 3 open issues with no assignee
e.g. INTEL-856, INTEL-857, INTEL-866
2026-09-16 0d new

SOP Monitoring 1

SeverityFindingFirst seen iAgeState i
medium SOP Monitoring: 2 open issues with no assignee
e.g. INTEL-310, INTEL-311
2026-09-11 5d standing

IntelgicPOC 1

SeverityFindingFirst seen iAgeState i
medium IntelgicPOC: 1 open issues with no assignee
e.g. INTEL-527
2026-09-11 5d standing

Resolved since the last run i

FindingFirst seenOpen for
INTEL-106 — Live plant credentials committed to the repository (incomplete scrub)2026-09-115d
INTEL-263 — Integrate SRI-8120 SDK/driver and establish device communication2026-09-115d
INTEL-265 — Build the 3D point-cloud/profile data processing pipeline2026-09-115d
INTEL-266 — Build visualization of the captured 3D profile in the Certainty Core2026-09-115d
INTEL-283 — Kalpataru steel plate measurement inspection through 3d profiler POC2026-09-115d
INTEL-288 — Imaging screen: replace defect-type button grid with a searchable sing2026-09-115d
INTEL-289 — Hardware Setup for testing environment (Rhitban & Madhusudan)2026-09-115d
INTEL-290 — Linux System setup (For Testing with integrated hardware) -Atul2026-09-115d
INTEL-60 — [MadhuSudanM-Intelgic] DOC: Certainty AI Tech Doc2026-09-115d
INTEL-62 — [pabitra-intelgic] 3D-Profiler (SRI-8120) With One profiler (Note: Mul2026-09-115d
INTEL-63 — [Roddur-Intelgic] Robotics Implementation (Movement, Dynamic capture p2026-09-115d
INTEL-65 — [nirupamj-intelgic] Site Admin Dashboard2026-09-115d
INTEL-11 — Onboarding: Jira/GitHub access, review workspace docs2026-09-115d
INTEL-112 — No CI has ever existed, while a working quality gate sits unwired2026-09-115d
INTEL-116 — Auth model gaps: device-scoped WebSocket auth and fail-open session va2026-09-115d
INTEL-117 — Architecture and dependency debt (non-blocking)2026-09-115d
INTEL-13 — Coordination sync with Derek/Erven on QA scope split2026-09-115d
INTEL-15 — QA-E6: Draft HIL (hardware-in-the-loop) bench requirements outline (wi2026-09-115d
INTEL-16 — Onboarding: GitHub access, review workspace docs + example repo CI wir2026-09-115d
INTEL-18 — INF-E4: Draft CI/CD pipeline spec -- Python linting standards, test ru2026-09-115d
INTEL-19 — CERT-E5: Python test-coverage baseline plan for the decisioning path2026-09-115d
INTEL-30 — AWS access monitoring + pipeline-failure alerting setup (ties to Rajes2026-09-115d
INTEL-31 — INF-E4: CI/CD pipeline monitoring dashboards + alert tuning2026-09-115d
INTEL-32 — QA-E6: HIL bench procurement research (vendor/spec options)2026-09-115d
INTEL-33 — Review real Certainty Python codebase structure + first real PR review2026-09-115d
INTEL-34 — INF-E4: Finalize CI/CD lint/test pipeline against real repos2026-09-115d
Dynamic Defect Types (Stakes): 1 open issues with no assignee2026-09-115d
SSO for Certainty Client: 2 open issues with no assignee2026-09-115d
certainty-client #29 merged with no review2026-09-115d
certainty-client #30 merged with no review2026-09-115d
certainty-client #32 merged with no review2026-09-115d
certainty-core #41 merged with no review2026-09-115d
certainty-core #43 merged with no review2026-09-115d
certainty-core #47 merged with no review2026-09-115d
certainty-core #48 merged with no review2026-09-115d
certainty-core #51 merged with no review2026-09-115d
certainty-core #52 merged with no review2026-09-115d
certainty-core #53 merged with no review2026-09-115d
certainty-core #54 merged with no review2026-09-115d
certainty-core #55 merged with no review2026-09-115d
certainty-core #56 merged with no review2026-09-115d
certainty-core #57 merged with no review2026-09-115d
certainty-core #58 merged with no review2026-09-115d
certainty-core #60 merged with no review2026-09-115d
certainty-license #34 merged with no review2026-09-115d
certainty-license #35 merged with no review2026-09-115d

Hours logged

Time logged in Jira worklogs. This week is 2026-09-14 to 2026-09-20; overall is everything recorded on or before 2026-09-20. Both scales run to the same maximum, so a bar in one chart can be compared with a bar in the other.

This week

taylor: 0.00 hours; Derek: 9.92 hours; devin: 3.00 hours; Erven.j: 0.00 hourstaylor0.00hDerek9.92hdevin3.00hErven.j0.00h

Overall

taylor: 106.50 hours; Derek: 71.60 hours; devin: 50.90 hours; Erven.j: 8.50 hourstaylor106.50hDerek71.60hdevin50.90hErven.j8.50h
PersonThis week Overall
taylor0.00h106.50h
Derek9.92h71.60h
devin3.00h50.90h
Erven.j0.00h8.50h
Total12.92h 237.50h

Only 4 people log time in Jira. Everyone else on the board has no worklogs at all, which is a logging habit rather than a measure of their work, so they are left off this view rather than shown as zero. Hours are counted by the date each worklog is recorded against, read from Jira on 2026-09-16; a worklog's date is only as accurate as whoever set it.