Reporting pack files
Which files make up the pack: the workbook, the deck, and the memo, with their formats and how often they recur.
Wolf Suite early access
Request suite qualification
Wolf Suite early access is not purchasable yet: a sale requires an approved agreement and a qualified release. Qualification reviews one real reporting pack against the named supported workflow so the release decision is based on evidence, not a form.
What to include in your request
Approved edits
Exactly what the pipeline may change: the approved values, text, or fields in each file, and what triggers a run.
Preserved features
What must not change: charts, pivots, macros, layouts, speaker notes, styles, or any part a reviewer depends on.
Target applications
What opens the outputs: the applications and versions (for example Microsoft Excel, PowerPoint, Word, or LibreOffice) the saved files must satisfy.
What the qualified demonstration covers
The reporting workflow behind the suite is exercised as a bounded, synthetic demonstration. For the FY2026 Q1 example period it applies revenue 125.13, costs 75.12, and total 200.25 USD millions, synthetic demonstration data whose total is the stated sum of the other two values.
- From one approved dataset, edits to three existing files are saved into a new output bundle: workbook cells, an editable presentation chart and table, and memo table cells and text runs. The input files are preserved untouched, and reference content is left unchanged.
- A stale memo target and an existing output destination are both refused before anything is published, and the inputs are checked unchanged after each refusal.
- The running job is killed at three verified boundaries (between operations, immediately before, and immediately after publication), resumed, and each operation is proven to execute exactly once; cancellation and tampered staged output have separate refusal checks. Recovery is proven for those process kills only, not for storage loss.
- Every saved file is reopened and inspected by independent readers: the workbook check asserts the intended values, the reporting period, and an untouched reference cell, and the deck and memo checks compare untouched package members byte for byte.
The full walkthrough, including the exact synthetic example files and retained original presentation renders, is in the technical article.
Evaluation requirements
When a review reaches a hands-on evaluation, the demonstration runs offline from a candidate bundle under these requirements.
Qualified platforms
macOS on Apple silicon (arm64) or Linux on x86_64, with a CPython 3.13 engine environment. Windows, other architectures, and other environments are unqualified.
Python requirements
uv and CPython 3.13 must already be installed. The runner script executes under your system python3 and builds the engine environment; alternate Python ABIs are unqualified.
Offline install
Installation uses only the bundled platform wheelhouse, with package indexes and downloads disabled. No network access to package sources is used.
Fresh run destination
The demonstration requires an output directory that does not yet exist. A run pointed at an existing directory is refused rather than overwritten, so a rerun can never clobber an accepted bundle or its records.
Release boundary
A private reporting candidate passed the workflow, refusal, and recovery qualification on macOS arm64 and Linux x86_64. That is private candidate qualification, not public package readiness: candidate distribution remains private pending release review, it grants no suite evaluation or purchase rights, and WolfXL's existing evaluation path is unchanged.
- No candidate download is offered on this site. Candidate distribution remains private pending release review.
- Any suite evaluation would require its own approved scope for the DOCX and control-plane components. The commercial license texts bundled with the candidate are adopted terms, not an evaluation grant.
- WolfXL's existing evaluation path is unchanged: a named-person, 30-day, no-fee, non-production evaluation under accepted evaluation terms, requested and credentialed through the existing process.
- Suite sales stay closed until an agreement is approved and a qualified public release exists. Requesting qualification creates no obligation and is not a purchase or a preorder.
A public-safe summary of the current candidate's archive identity, verification record, retained native-application boundaries, and example-file hashes is published as the candidate summary record. It identifies the private candidate for review purposes and authorizes no distribution, evaluation, or use.
How qualification works
The reply is an initial scope decision: whether the described pack fits the named supported workflow, which requested features are unsupported today, and whether a scrubbed or synthetic example review would add useful evidence. It is a fit decision, not access; no download, evaluation grant, release date, or purchase priority follows from it.
- The review happens by email. Describe the pack and the workflow; no file is uploaded to this site.
- If an artifact is needed later, use a scrubbed or synthetic copy agreed in the review.
- Requesting qualification is free, creates no obligation, and is not a purchase or a preorder.
- Qualification does not promise a release date; the suite goes on sale only with an approved agreement and a qualified release.
- Existing WolfXL subscriptions, prices, and rights are unchanged whether or not you request qualification.
Compose the request email
This site sends nothing. The button opens your own mail client with a prefilled template addressed to [email protected]; review and send it yourself.