StackJack 0.1.0.15196+6879e6c
StackJack 0.1.0.15196+6879e6c
This release reworks how AI Governance works with your own storage. When your storage is the main store, your audit trail, report packs and older captured text can be kept there, and StackJack can read them back when you need them. Most AI Governance pages also have a new, more consistent layout, including the Data sources, Deploy, Storage archive and alert pages.
New features
- Records in your own storage. Your audit trail (one file per day) and your report packs are now written to your organization's own storage, on every plan. When your storage is the running main store, StackJack keeps the last 400 days of the audit trail and 90 days of each report pack file. Older records are kept only in your storage. StackJack still keeps the daily integrity record and each pack's fingerprint for six years.
- StackJack checks your storage before removing its copy. Before StackJack deletes its own copy of an older record or older captured text, it checks again that the item is still in your storage and unchanged. If the item is missing, StackJack writes it back first. If the storage holds a different file or does not respond, StackJack keeps its copy.
- Older captured text moves to your main store. While your main store is running, StackJack deletes its copy of each older text item once that item is confirmed in your storage. A storage used as an extra copy works as before: StackJack keeps its own copy until the keep time ends.
- Read older audit days from your storage. When older audit entries are only in your storage, the Audit trail page shows a panel where you pick a day and select Show the day. StackJack reads that day from your storage and checks it against the daily integrity record. If a day does not match, it is still shown, with a warning. If the storage cannot be reached, the page says so.
- Where each report pack file is. The Report packs page has a new Where the file is column. Downloading a pack that is only in your storage reads it back and checks it against the pack's fingerprint. If the check fails, the problem is shown on that row instead of a broken download.
- "What StackJack keeps" card. The Audit trail, Report packs and Storage archive pages show a card that explains what StackJack keeps and what is only in your storage.
- Confirmation phrase when removing a storage. Removing a storage that holds records StackJack no longer has now requires typing a confirmation phrase. The dialog shows how many of those records there are and from which date.
- Closing AI Governance warns about records in your storage. Before you close, the Close card lists the older audit entries and report pack files that are only in your storage. After the close, StackJack can no longer read them for you.
- Data-subject export shows where the access log starts. The export's README gives the date of the first access-log entry StackJack holds. If older entries are in your own storage, the README says so.
- MCP tools for the same information:
- The audit trail tool lists the days that are only in your storage, and a new optional
dayparameter reads one of those days back. - The evidence pack tool shows where each pack's file is.
- The storage tool reports each storage's role, its state and a one-line explanation.
- The alert tool returns the same context as the alert page.
- The setup status tool reports your sources, the places they cover and any gaps.
- Mark a source as "Not using this". On the Data sources page and in Get started, you can mark a capture method you don't use. It moves to a "Not used" group, and StackJack stops asking you to set it up. Marking a source this way does not switch anything off.
Improvements
- Own storage on every plan. You can use your own storage, as an extra copy or as the main store, on every plan. On Free, only records are stored, not captured text.
- Business plan features. The Business plan includes the SIEM alert channels (Microsoft Sentinel, Splunk HEC, syslog over TLS, OTLP export), readiness for each client organization, legal holds, and own storage as the main store.
- Stored-text cap and main-store text. Text going to your own main store does not count as text stored with StackJack. The stored-text cap therefore never pauses capture for an organization whose new text goes to its own main store.
- Data sources page. The page now shows the sources you use, the places they cover and any gaps. Each source shows one of these states: "Working", "Waiting for data", "Not connected", or "Needs Pro" / "Needs Business".
- Scheduled sources count as working. A source StackJack reads on a schedule counts as working as long as its last read had no problem.
- Client health on All clients. Each client row's health is now based only on the sources that client actually uses.
- Alert detail pages. Each alert kind's page now shows the context needed to act on it. Coverage alerts are raised once per computer and once per gap, instead of repeating.
- Storage Archive page. The page has been rebuilt:
- One card per storage, showing its role, a single state with an explanation, its figures, a keep-time meter and a records line.
- Connecting a storage takes four numbered steps.
- The connection test shows four lines (sign in, write, read back, try to overwrite) and one sentence saying what to fix.
- Choosing a mode uses two clear cards. If the main store can't be chosen, the card says why.
- Storage cost panel. A cost panel shows how much of your text is stored with StackJack.
- Deploy to staff computers. The page now has:
- Two product cards and three numbered steps.
- Deployment method cards: Microsoft Intune (recommended), Group Policy, Script, and macOS and Linux.
- A side panel with reach, your enrollment key or browser token, and package details.
- A tooltip on a disabled Copy script button explaining why it is unavailable.
- Clients and standards, Drift, and Deploy to a client. The five setup cards are replaced by a single setup rail that highlights the step to do now.
- Check now shows a short line explaining why it is unavailable or when the last check ran.
- Add a standard is available as soon as any standard is published.
- Rule editing. The rule panel has four tabs and a fixed Save button at the bottom. If you close it with unsaved changes, it asks before closing.
- Product tours. Tours no longer reappear on their own. Show the tours again is in the Help menu and asks before restarting them.
Bug fixes
- Text capture now pauses correctly when your main store's buffer is full. It resumes automatically once the buffer drops below 80 percent.
- Text already on its way to your main store is now finished when you choose Stop using as main store.
- A main-store write that is never confirmed is now counted as lost only once.
- The storage card no longer describes a main store as "Working. Copies run on a schedule."
- Privacy and retention page:
- The keep-time notes for the audit trail and evidence packs are now accurate whether or not a main store is running.
- The storage summary now includes text kept only in your storage.
- The error shown when a keep time is set below six years now describes the setting itself.
- Storage wording on a client organization's pages no longer says that the audit trail is written to that organization's storage. The audit trail is a single record for your whole account and goes to your own organization's storage.
- With a client organization selected, the Storage archive page and the Close card now show your own organization's records, if you have Administrator or Auditor access to it.
- The report pack list mentions the 90-day keep time only while it actually applies. A keep time that has passed now says StackJack "may" remove its copy from that date.
- A source that is in use but not connected now shows "Not connected" (previously "Not set up") on the Overview and in Get started.
- In Get started, unticking a goal now also unticks the sources it added.
- The Deploy page no longer shows an empty reach bar when no computers are enrolled.
UI & UX changes
- Consistent layout. Almost every AI Governance page now uses the same layout:
- Sections appear as panels, and page buttons sit in the page header.
- Empty lists show a short message inside their panel.
- Each page has a single primary (filled) button for the next thing to do.
- Fewer empty figures. Rows of figures that are all zero are hidden, with one line saying when the numbers will appear. This applies to Spend, Incidents, Get started results and Clients and standards.
- Detail pages. Incidents, approvals, tool requests, vendor changes and inventory items share one layout: the main details on the left and key facts in a side column.
- Destructive buttons. Buttons that delete or disconnect are shown as red outlines and still require a confirmation.
- Wider pages. AI Governance pages use a wider content column.