Status: The deployment is live with one use case (Ticket Routing), but the roadmap is stalled. A new security vulnerability was found by CTT on 22 Oct and a fix is in progress (DEP-697).
Shipped (last 7 days):
In progress:
Blocked:
Next milestone: Use case · Accounting Agent, no date agreed.
Auto-updated from Linear on 2026-10-25.
Estimate set 14d ago by vicente@noxus.ai
| Deployment | Version | AI Ops | Capacity | MoM | Overage | Token $ | Tenants |
|---|---|---|---|---|---|---|---|
| CTT - PRODdeployed | 1.9.03d behind | 323K | 7.1% | +67.8% | — | $289.57 | 2 |
Nothing outstanding on our side.
No actions recorded.
5 open · 1 past the date we needed them by
[Linear DEP-632 · b2299c43] Unblocks defining the next use case and the roadmap.
Waiting on Carlos Machado Silva · raised 20 Oct 2026 (6d ago) · needed by 23 Oct 2026
Historically the main blocker: every flow waits for CTT's internal architecture team sign-off regardless of technical readiness.
Waiting on Carlos Machado Silva · raised 27 Aug 2026 (60d ago)
[Linear DEP-677 · 2ef23533] Unblocks platform outbound connectivity for required external domains.
Waiting on Rodrigo M. Ribeiro · raised 22 Oct 2026 (4d ago) · needed by 27 Oct 2026
[Linear DEP-678 · 7021ad1d] Unblocks demo of image handling and review of CTT's internal model comparison.
Waiting on Rodrigo M. Ribeiro · raised 22 Oct 2026 (4d ago) · needed by 27 Oct 2026
David prefers Power Platform, where someone is already building similar eligibility logic. Needs a compelling demo to unblock.
Waiting on David Gutierrez Arellano · Temporary Workers Agent · raised 27 Aug 2026 (60d ago)
[Linear DEP-298 · 02397ffc] Unblocks the chat widget deployment.
Waiting on CTT · raised 11 Oct 2026 (15d ago) · needed by 08 Oct 2026
Flagged in July: no invoice received from CTT. Rodrigo to follow up with Carlos Sobrício. Noxus billing contact: João Pedro.
Waiting on Rodrigo M. Ribeiro · raised 27 Aug 2026 (60d ago)
[Linear DEP-195 · 64fc9718] **Action:** Confirm that the corrected calculation has been applied to the existing analytics data (not only to new data going forward), then tell CTT it is fixed. **With whom:** Lourenço Lúcio (Noxus), the confirmation sits with him. **Done when:** the corrected figures are verified in the analyti. Covered by DEP-195, done on 2026-09-23. Was: Incorrect calculation found in the analytics DB; fix implemented but the DB correction still needs confirmation.
Waiting on Lourenço Lúcio · raised 27 Aug 2026 (60d ago)
[Linear DEP-196 · ecc8fa83] **Action:** Get a date from Engineering for Git-style sync between environments. If there is no near-term date, agree with CTT that manual export / reimport is the standing process and document it for them. **With whom:** Noxus Engineering / Product, no named owner yet; naming one is the first step. Covered by DEP-196, done on 2026-09-23. Was: No ETA for Git-style environment sync; current workaround is manual export/reimport between environments.
Nobody named · Azure dedicated instance (VMs + PostgreSQL) · raised 27 Aug 2026 (60d ago)
Luís Tunes (AdvanceWorks) prefers log-prob; João Vicente prefers an agent-calculated score. Pending test validation.
Waiting on João Vicente · Ticket Routing & Categorisation Agent (HR tickets) · raised 27 Aug 2026 (60d ago)
[Linear DEP-440 · d16a5aa8] Unblocks CTT's penetration testing of the new chat widget endpoint.
Waiting on lourenco@noxus.ai · raised 12 Oct 2026 (14d ago)
Use cases, infra deployment and process transformation — each with its own stage timeline and SLA
Dedicated Noxus instance on CTT's own Azure: VMs + PostgreSQL, models via Azure AI Foundry (EU-only), external calls through CTT's API gateway. Editor V2 not yet activated in their workspace; per-node usage metrics being added as output nodes (target end of Aug 2026).
Categorises and routes HR/employee tickets received by email (GoContact) to the correct queue — ~20k tickets/yr across CTT + GBE queues. Dispatcher runs every 4h (fetch → table), processor every 5 min. Migrated from manual OpenAI calls to the native AI agent node; ~€0.03/execution; retries run outside 07h–20h polling. New architecture built for the September school-year spike (>1,000 tickets/cycle).
Confirmed next use case (priority #1), including invoice-correction logic. Scope to be confirmed with Carlos Machado Silva.
Priority #2 after the Accounting Agent. Details TBD.
Receive candidate file by email (trabalho.temporario@ctt.pt) → apply eligibility rules (today a large Excel) → write to Oracle DB or notify the temp agency (ETT). Low build complexity. Blocked: David (CTT director) prefers Power Platform, where similar logic is already being built.
Replace manual Excel-based eligibility process for temporary workers; CTT's own estimate ~€120k/yr.
7 active
Decision-maker for AI agents
Approves architecture and new use-case scope; escalation point for integrations. Attends weeklies.
CTT Express — digital / innovation lead
Separate CTT Express workstream: map ~50 use cases, pick 10 best fits (CRM, SAP automation). Also the director who prefers Power Platform for the Temporary Workers case.
Technical lead / project manager
Main day-to-day contact; attends all weeklies. Chasing the missing invoice with Carlos Sobrício.
Technical — built the classifier flow
Strategic (CTT Express expansion meeting)
Implementation partner (AdvanceWorks)
External builder — implements flows via the Noxus SDK. Prefers log-prob for confidence scoring (vs João Vicente's agent-calculated score).
Strategic (CTT Express expansion meeting)
0 open of 4 · 1 missed SLA · 67% met
Nothing open.
What could still go wrong. Open risks subtract from health — less than a penalty, because they haven't happened yet.
Editor V2 not activated in CTT workspace
CTT was unaware Editor V2 existed; not activated in their workspace. They are building on the older editor.
Mitigation: Activate Editor V2 in CTT's workspace and walk Rodrigo/Luís through it.
jose@noxus.ai · logged 2mo ago
September ticket-volume spike (>1,000/cycle)
School-year restart expected to push HR ticket volume above 1,000 per cycle.
Mitigation: Dispatcher + table architecture was designed for this; monitor throughput and retry queue through September.
jose@noxus.ai · logged 2mo ago
Pulled from Granola and filed here by attendee domain. Read-only — edit them in Granola.
No meetings filed here yet. Set the customer's email domains above and they arrive on the next sync.
Everything we have sent this customer. Links only — the file stays where it lives.
Nothing attached yet.
Context, commitments, gotchas — anything without a field of its own. Claude reads and writes these over MCP; pinned notes come first.
No notes yet.
Incidents held against the account. Open ones subtract from health; resolved ones decay over 90 days.
No penalties logged.
Stage transitions, newest first