Questory
A quest-and-story app for kids: habits, reading and a virtual pet.
Designed and built solo by AJ Pardilla, with AI agents as the engineering team.
AJ Pardilla
I spent twenty years designing and building products. Now I build the agents that build them with me.
VP of Product and AI, Unicity International
I lead product and AI at Unicity International: 13 direct reports, 8 product teams, and the checkout and payments stack for more than 50 markets. This is my design portfolio. The work on show is the agents I built, with what I taught each one and how I check it.
The register, current at 18 September 2026
75 agents across 12 systems.
30 run on a clock, 33 on command. The other 12 are built and waiting for command.
The register
12 systems, ordered by what actually runs. Open one to meet its agents
How I checked
54 of these were read out of the files on my own machine. 21 are Grok bots, seen running in my workspace on 18 September 2026. Each entry says which.
The method comes with me. Agents built inside a company stay there, and get rebuilt inside the next one under its rules.
75 of 75 shown
No agent matches that. Clear the field, or choose All.
Mobile app team
16 agents, 16 running
A sixteen-role software team for a mobile app: research, plan, design, build, test, review, release.
The 3 receipts in this system all come from one production run on 21 August 2026.
Show the 16 agentsHide the 16 agentsChief of Staff, Researcher, Planner and 13 more
001Analytics SpecialistDecides what a change should measure: which event, against which baseline, and how success gets judged.on command
- What I taught it
Never invent metrics or claim a launch proved success by itself.Do not fabricate data, declare KPI impact from release alone, query protected data without authority, write providers, approve work, or create agents.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read analytics contracts
- Read KPI strategy
- Run local instrumentation checks
- Emit analytics decision
002Backend SpecialistAdvises on API and service changes, request, response, error and compatibility behaviour, and names the contract tests that must pass.on command
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read backend code
- Read API contracts
- Run local contract tests
- Emit backend guidance
003Chief of StaffSorts an incoming task, ties it to the project's strategy pack, and assembles the smallest qualified team of other agents.on command
- What I taught it
The dispatcher can't change anything in a live system, approve work, or leak its thinking.Do not perform provider writes, approve a handoff, or expose private reasoning.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read project pack
- Classify risk
- Request role through control plane
- Emit work order draft
004Data SpecialistDesigns and reviews database schema and migration work on paper, order, rollback, verification queries, with no access to live data.on command
- What I taught it
It designs database changes but is never allowed to run them live.Do not apply a migration, change live data, use production credentials, approve the candidate, or create agents.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read schema
- Read migrations
- Run local database tests
- Run nonmutating dry run
- Emit data guidance
005DesignerTurns an approved plan into accessible mobile screen designs covering every state: loading, error, empty and translated text.on command
- What I taught it
Never touch or influence the independent QA checking your own design.Do not act as, select, prompt, dismiss, or edit the findings of Independent UX QA.
- How it is checked
- When design QA is required, a separate Independent UX QA agent judges the design before plan approval, in a session the Designer cannot share.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read project pack
- Read research packet
- Create design artifacts
- Emit prototype manifest
006EngineerWrites the code for one approved slice of a plan, in its own isolated workspace, and reports exactly what it covers.on command
- What I taught it
Never grade your own code or rewrite the rules to pass.Do not approve your own work, change acceptance criteria, or create other agents.
- How it is checked
- Always graded by the Evaluator in a separate session from the Engineer, and on the higher QA tiers also reviewed by a separate Independent Reviewer, against agents.
- What it made
- Wrote a small, fully tested code change inside its own isolated workspace, and a separate reviewer agent cleared it, start to finish in about two minutes, with no human writing any of the code.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read repository
- Workspace write
- Run local checks
- Emit candidate evidence
- Request role through control plane
007EvaluatorGrades finished work against a fixed rubric and hard pass/fail gates before it is allowed to ship.on command
- What I taught it
One serious problem can't be smoothed over by a good average score.Do not average away a veto, override a hard gate, or approve merge, data, build, submit, or release.
- How it is checked
- The Evaluator is the grader, so it is bounded from outside: a fixed craft rubric it is forbidden to improve plus hard gates enforced deterministically by the control plane, not by the Evaluator.
- What it made
- Independently graded a plan written by another AI agent against a fixed rubric before it was allowed to proceed, and recorded a 100-out-of-100 pass with zero hard blockers.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read handoff artifacts
- Run deterministic gate checks
- Grade rubric
- Emit coverage receipt
008i18n SpecialistChecks new customer-facing text is translatable, that every language stays in sync, and that translated text still fits on screen.on command
- What I taught it
Never make up a translation and pass it off as translator-approved.Do not invent translator-approved copy, overwrite shared translation sources, write providers, approve work, or create agents.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read locale files
- Read translation governance
- Run i18n checks
- Emit i18n decision
009Independent ReviewerReviews the engineer's code diff adversarially, without reading the engineer's own write-up first, and returns evidence-backed findings.on command
- What I taught it
A clean review must prove it actually looked, not just say fine.Limit ordinary findings to five, deduplicate them, and make zero-finding reviews falsifiable.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric, and required to run in a session separate from the Engineer it reviews.
- What it made
- Reviewed another AI agent's code diff blind, the system physically withholds that agent's self-assessment, and signed off only after checking the change against each acceptance criterion itself.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read candidate diff
- Read acceptance contract
- Run readonly checks
- Emit review findings
- Request role through control plane
010Independent UX QAChecks design quality before a plan is approved, then checks the finished build against the approved design.on command
- What I taught it
Every applicable screen state needs its own real screenshot, not a generic stand-in.Do not approve your own work or substitute generic screenshots for state coverage.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read intake
- Read research
- Read design artifacts
- Read candidate visual evidence
- Emit UX findings
011Mobile SpecialistAdvises on iOS and Android behaviour, navigation, lifecycle, storage, timing, and sets the device test matrix for a change.on command
- What I taught it
Never claim a device test ran when it didn't, and never relax the QA bar.Do not lower mobile QA, claim unrun device evidence, write providers, approve work, or create agents.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read mobile code
- Read platform contracts
- Run local mobile checks
- Emit mobile guidance
012PlannerTurns research and product direction into the written implementation plan the rest of the pipeline builds from.on command
- What I taught it
Unresolved product decisions have to surface, not get buried in engineering tasks.Do not hide unresolved product decisions inside engineering instructions.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- What it made
- Turned research into an implementation plan that a separate evaluator agent scored 100 out of 100 against a fixed rubric, after three rounds of being sent back, before any code was written.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read project pack
- Read research packet
- Read design artifacts
- Emit markdown plan
- Emit HTML explainer
- Request role through control plane
013QA EngineerTests a finished build against its acceptance criteria, including failure and offline paths, and captures screenshots and logs as evidence.on command
- What I taught it
A generic 'it loads' test doesn't count as real coverage.Do not substitute a generic smoke test for task-specific acceptance coverage.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read candidate
- Run test commands
- Request mobile runner job
- Read test artifacts
- Emit QA manifest
014Release OperatorRuns only the exact release step it was pre-authorised for, then confirms it happened using the provider's receipt.on command
- What I taught it
A good score, a passed QA run or a deadline never adds up to permission to build a release.Do not infer build authority from submit authority, QA, a rubric score, or urgency.
- How it is checked
- Executes only the exact operation authorized by a consumed, target-bound capability from the broker, and must emit a provider receipt plus fresh readback evidence for each named operation.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read release policy
- Run nonmutating release preflight
- Prepare brokered release intent
- Read provider receipt
015ResearcherProduces sourced competitor, product, UX and technical research to brief the planner before a feature is built.on command
- What I taught it
Research informs the decision; it never makes the decision up.Do not select the product decision, write the canonical plan, or fabricate market evidence.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- What it made
- Wrote a sourced research brief, citations, findings and explicit limitations, that kicked off a real planning cycle inside a self-built multi-agent engineering pipeline.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read project pack
- Read workspace
- Web research
- Emit research packet
016Security SpecialistReviews login, privacy, credential and permission changes for abuse cases and fail-closed behaviour, independently of the engineer.on command
- What I taught it
It flags security risks but never touches real secrets or live systems.Do not handle production secrets, weaken controls, run destructive tests, write providers, approve a release, or create agents.
- How it is checked
- Graded by the Evaluator agent against this role's fixed 15-point craft rubric.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Read security contracts
- Read candidate diff
- Run safe negative tests
- Emit security findings
Product Command Center
15 agents, 15 running
Gathers signals from Slack, ClickUp, mail and calendar, writes the morning brief, then reviews itself.
Show the 15 agentsHide the 15 agentsPCC v3 Daemon (pccd), PCC Briefing Writer, PCC Collector: Slack and 12 more
017PCC Accuracy ReviewerChecks every briefing item written this run for a source link, real evidence and the right person, then debates findings with the other reviewers.on a clock
- How it is checked
- Its findings go through a live 2-3 round debate with the relevance and completeness reviewers before the lead applies any fix.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Synthesis and signals API (read)
- SendMessage (reviewer debate)
018PCC Briefing CriticChecks the draft briefing against the actual database items, nothing urgent missed, calendar conflicts noted, and sends feedback back for one revision.on a clock
- How it is checked
- It is itself the check on the briefing writer, and its own feedback triggers one mandatory writer revision before the lead posts the briefing.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Items and calendar (read)
- SendMessage (to the writer)
019PCC Briefing WriterDrafts AJ's daily briefing in plain spoken prose from the current items and calendar, most urgent first, then hands it to the critic.on a clock
- How it is checked
- A second agent, the briefing critic, reviews the draft against the real database items and sends it back for revision before it ships.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Items and calendar (read)
- SendMessage (to the critic)
020PCC Collector: ClickUpPulls active and blocked ClickUp tasks for AJ's tracked teams and posts them to the briefing system as signals.on a clock
- How it is checked
- Its output is cross-checked by the completeness-reviewer phase for gaps and duplicates; that review runs after the items are written, and the lead then applies fixes or drops the items the reviewers agree on.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- ClickUp (via MCP)
- Bash (posts to the ingest API)
021PCC Collector: Gmail + CalendarPulls Gmail and Google Calendar signals for the daily briefing, falling back to the Google connectors when the command-line collector is broken.on a clock
- How it is checked
- The pre-flight connector probe treats the Gmail/Calendar path as nice-to-have with a documented degraded mode rather than a hard stop, and the completeness-reviewer phase then checks its coverage before the lead finalizes items.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Bash (Google Workspace CLI collectors for Gmail and Calendar)
- Gmail and Google Calendar (via MCP, fallback only)
022PCC Collector: SlackSearches AJ's priority Slack channels and posts what it finds to the briefing system as signals.on a clock
- How it is checked
- Its signals are validated by the required-connector pre-flight probe (a broken Slack MCP call halts the whole refresh) and later by the completeness-reviewer.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Slack (via MCP: search and read threads)
- Bash (posts to the ingest API)
023PCC Collector: TelegramRuns the Telegram collector script, reads the signals it produces, and posts them to the briefing system.on a clock
- How it is checked
- Its liveness is checked by an automated heartbeat watchdog that pages if the listener goes silent for more than 10 minutes.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Bash (Telegram collector script)
- Bash (posts to the ingest API)
024PCC Completeness ReviewerChecks that every important signal this run, incidents, blockers, direct asks to AJ, became an item, and flags duplicates.on a clock
- How it is checked
- Its own findings are debated live with the accuracy and relevance reviewers for 2-3 rounds before the lead applies any fix.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Signals API (read)
- SendMessage (reviewer debate)
025PCC Pattern DetectiveGroups this run's poorly rated items by cause and proposes config fixes: new stop words, tighter thresholds, better filters.on a clock
- How it is checked
- Its proposed fixes go through a debate to consensus with the signal-auditor and synthesis-auditor before the lead applies only the safe ones.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Ratings API (read)
- SendMessage (debug-team debate)
026PCC Relevance ReviewerCompares this run's items against what AJ has rated badly before, and pushes the team to demote or drop repeat offenders.on a clock
- How it is checked
- Its challenges are debated live with the accuracy and completeness reviewers before the lead drops or keeps an item.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Ratings feedback API (read)
- SendMessage (reviewer debate)
027PCC Signal AuditorReviews the last run's raw signals for self-referencing content, stale ClickUp tasks slipping through, and wrong attribution.on a clock
- How it is checked
- Spawned only when 3 or more items were rated 2 or lower in the last 24 hours (the threshold is a config setting), and its findings must reach debate consensus with two other auditors before any fix is applied.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Signals API (read)
- SendMessage (debug-team debate)
028PCC Snapshot Team WriterWrites one tracked team's person and team snapshots, proposes items needing attention, and cross-checks with the other team writers before anything is saved.on a clock
- What I taught it
When people disagree, report both positions and who is deciding, never a winner.Never silently pick one side.
- How it is checked
- Every writer cross-checks its proposed items against the other 8 team writers via a live message round before the lead writes anything to the database.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Tools it may use
- Synthesis API (person and team snapshots, item proposals)
- SendMessage (teammate cross-check)
029PCC Synthesis AuditorReviews briefing items that scored under 40 for confidence, looking for weak grounding or missing evidence.on a clock
- How it is checked
- Runs only when 3 or more items were rated 2 or lower in the last 24 hours (the threshold is a config setting), and its findings must reach debate consensus with the signal-auditor and pattern-detective.
- How I know
- Audited against the files on AJ's machine. Running status confirmed by AJ on 19 September 2026.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Items API (read)
- SendMessage (debug-team debate)
030PCC v3 Daemon (pccd)AJ's live briefing system: collectors gather signals, a gated Claude step writes the items and morning briefing, and urgent alerts reach him immediately.on a clock
- What I taught it
Don't make a solved problem sound like it's still open.Resolved means resolved. Never present a resolved item as pending.
- How it is checked
- Its own heartbeat is monitored by a watchdog process that pages if the daemon goes silent for more than 10 minutes, and separately if no briefing exists by 9am.
- What it made
- One always-on agent runs a full collect-synthesize-brief cycle roughly every half hour and leaves a dated output folder as a receipt for each run.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 18 September 2026
- How it runs
- Running under pm2 as process 'pccd' (status: online), alongside five sibling v3 processes also online: pcc-v3-incident-poller, pcc-v3-feed-sweep, pcc-v3-watchdog, pcc-v3-vip, pcc-v3-self-improve. It spawns a gated 'claude -p' synthesis session (SYNTHESIS_MODEL, BRIEFING_PROMPT_PATH) on each cycle.
- Runs on
- Anthropic Claude, Sonnet 5
- Tools it may use
- Read
- Write
- Grep
- Glob
031PCC Dashboard AssistantAnswers AJ's questions about team status, incidents and meetings inside his dashboard, reading a curated knowledge wiki before calling any live tool.on command
- How I know
- Audited against the files on AJ's machine.
- How it runs
- Chat assistant embedded in the PCC v2 web dashboard; it fires only when AJ sends it a message and has no schedule. Its standing instructions are the system preamble built in the dashboard's own code ('You are embedded in the PCC dashboard...'). The pm2 process that serves the dashboard ('pcc-web') is online today, so the surface is reachable.
- Tools it may use
- Slack MCP
- Gmail MCP
- Calendar MCP
- ClickUp MCP
- Supabase MCP
- Mixpanel MCP
15 agents in Product Command CenterPCC Accuracy ReviewerPCC Briefing CriticPCC Briefing WriterPCC Collector: ClickUpPCC Collector: Gmail + CalendarPCC Collector: SlackPCC Collector: TelegramPCC Completeness ReviewerPCC Pattern DetectivePCC Relevance ReviewerPCC Signal AuditorPCC Snapshot Team WriterPCC Synthesis AuditorPCC v3 Daemon (pccd)PCC Dashboard Assistant
The engineering pipeline
9 agents, 9 running
Takes one feature or bug from research to a graded, tested, committed change.
The 9 receipts in this system all come from one production run on 6 September 2026.
Show the 9 agentsHide the 9 agentspipe-researcher, pipe-spec-writer, pipe-planner and 6 more
032pipe-doc-writerUpdates the project's wiki, README and changelog so the documentation matches what was actually built.on command
- How it is checked
- pipe-grader scores it against its written rubric.
- What it made
- Updated six separate documents so a project's written record matched what was actually built, as part of a real, shipped production change.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 14 September 2026
- How it runs
- Invoked when a person types the pipeline command in a target repo. The standing role file lives in agent-pipeline; each invocation writes its stage-06 receipt into the target repo's own run folder. A stage receipt exists in three of the four runs found.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Edit
- Write
- Grep
- Glob
033pipe-graderScores one pipeline stage's output against that stage's rubric, blind, and writes the pass/fail the coordinator checks before continuing.on command
- What I taught it
Score the actual output, not how hard it tried.Grade the artifact, not the effort.
- How it is checked
- A deterministic lint hook checks the grade file's frontmatter is complete and refuses a 'pass' verdict written over any criterion scored below the rubric's threshold.
- What it made
- Independently scored every stage of a real production feature build against that stage's fixed rubric, and the next stage could not start until the score was in.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 15 September 2026
- How it runs
- The same pipeline mechanism. Standing role file; its output is the grades folder every run produces, one graded file per stage and retry.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Grep
- Glob
- Write
034pipe-implementerBuilds one work package from the brief at a time, test first, inside the approved file list, and finishes only when the checks pass.on command
- What I taught it
Prove the test fails first, then write the fix.Never write implementation code before its failing test exists.
- How it is checked
- pipe-grader scores it against its written rubric, and a separate stage (pipe-test-verifier) writes outside-in acceptance tests for every criterion and runs the full suite itself, rather than trusting the implementer's account.
- What it made
- Implemented the code for a real feature that was later merged, deployed and health-checked in production, working test-first inside its own isolated workspace.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 14 September 2026
- How it runs
- The same pipeline mechanism. Standing role file; stage-04 output is written per work package inside each run folder.
- Runs on
- Anthropic Claude, Opus
- Tools it may use
- Read
- Edit
- Write
- Bash
- Grep
- Glob
035pipe-plan-auditorRuns a Claude-versus-Codex adversarial audit of the technical brief before AJ approves it: ship, ship with caveats, rescope or incomplete.on command
- What I taught it
Do not fake agreement between the two reviewing models; dissent is preserved word for word.Never manufacture consensus.
- How it is checked
- pipe-grader scores it against its written rubric; its own output is a cross-model debate (Claude seat vs Codex seat) rather than a single self-check.
- What it made
- Audited a technical brief before it was approved and correctly flagged it as not ready, forcing the human owner to explicitly override the block before work continued.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 14 September 2026
- How it runs
- The same pipeline mechanism. Standing role file; stage-03b output is written inside each run folder.
- Runs on
- Anthropic Claude
- Tools it may use
- Read
- Grep
- Glob
- Bash
- Write
036pipe-plannerWrites the technical brief every later stage follows: data model, flow, API, frontend, tests, risks, docs and the ordered work packages.on command
- How it is checked
- pipe-grader scores the brief against its written rubric, and pipe-plan-auditor separately pressure-tests it in a cross-model Claude-vs-Codex audit before AJ approves it.
- What it made
- Wrote the complete technical brief, data model, process flow, an ordered work-package list, the tests required and thirty named risks, that every later stage of a production feature build followed.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 14 September 2026
- How it runs
- The same pipeline mechanism. Standing role file; stage-03 output is written inside each run folder.
- Runs on
- Anthropic Claude
- Tools it may use
- Read
- Grep
- Glob
- Write
037pipe-researcherMaps the part of a codebase a feature or bug touches, finds the test and lint commands, and ranks likely causes.on command
- How it is checked
- pipe-grader scores its receipt against its written rubric and writes a pass/fail grade file before the next stage can run.
- What it made
- Wrote the research stage of a multi-agent engineering pipeline that mapped a real production codebase and its test commands before any code was written.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 14 September 2026
- How it runs
- The same pipeline mechanism. Standing role file; stage-01 output is written inside each run folder.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Grep
- Glob
- Bash
038pipe-spec-writerTurns the research into one user story with acceptance criteria a test can check, or an expected-versus-actual write-up for a bug.on command
- What I taught it
Do not add filler requirements just to look complete.Never pad the criteria list to look thorough; each one must earn its place.
- How it is checked
- pipe-grader scores it against its written rubric; a fail routes the spec back before the next stage runs.
- What it made
- Turned research into a full acceptance-criteria spec for a real production feature, the kind of spec a test can actually check against, not a wish list.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 14 September 2026
- How it runs
- The same pipeline mechanism. Standing role file; stage-02 output is written inside each run folder.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Grep
- Glob
- Write
039pipe-test-verifierProves the build meets every acceptance criterion by writing its own outside-in tests, without trusting the implementer's claims.on command
- What I taught it
Do not claim a test proves something it does not check.Never mark a criterion covered when the test does not actually assert it.
- How it is checked
- pipe-grader scores it against its written rubric; the acceptance test files are frozen by SHA-256 digest, which the gate recomputes before the run can close, so a later stage cannot quietly weaken them.
- What it made
- Independently proved a finished build satisfied every one of its acceptance criteria by writing its own outside-in tests, rather than trusting the builder's word for it.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 14 September 2026
- How it runs
- The same pipeline mechanism. Standing role file; stage-05 output is written inside each run folder.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Edit
- Write
- Bash
- Grep
- Glob
040pipe-validatorReviews the finished change blind, from the spec, the brief and the raw diff only, grading each finding critical, important or minor.on command
- What I taught it
Do not invent problems for show, and do not shrink a real one to let the work through.Never manufacture findings to look rigorous, and never downgrade a real one to unblock the gate.
- How it is checked
- pipe-grader scores it against its written rubric; it reviews blind (spec, brief and raw git diff only, never the builders' own account) and the run cannot close while it reports any critical or important finding.
- What it made
- Ran a blind review of the final code diff, without seeing what the other agents said about their own work, and cleared it with zero critical or important findings.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 15 September 2026
- How it runs
- The same pipeline mechanism. Standing role file; stage-07 output is written inside each run folder.
- Runs on
- Anthropic Claude
- Tools it may use
- Read
- Grep
- Glob
- Bash
9 agents in The engineering pipelinepipe-doc-writerpipe-graderpipe-implementerpipe-plan-auditorpipe-plannerpipe-researcherpipe-spec-writerpipe-test-verifierpipe-validator
The trading desk
8 agents, 8 running
Eight bots argue a trade. Risk can veto it, and no order is placed without AJ.
Show the 8 agentsHide the 8 agentsTrader, Risk, Bull and 5 more
041BearBuilds the case against a trade on AJ's trading desk.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Midday desk cycle
- Runs on
- xAI Grok
- Tools it may use
- Research stack
- Desk handoff
042BullBuilds the case for a trade on AJ's trading desk.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Midday desk cycle
- Runs on
- xAI Grok
- Tools it may use
- Research stack
- Desk handoff
043FundamentalsTrading-desk analyst covering company filings and fundamentals.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Midday desk cycle
- Runs on
- xAI Grok
- Tools it may use
- Filings
- Fundamentals data
044NewsTrading-desk analyst covering market news.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Midday desk cycle
- Runs on
- xAI Grok
- Tools it may use
- Market news
045RiskReviews position size and risk before any live trade on AJ's desk.on a clock
- What it may never do
- Holds a veto: the chair is blocked until Risk clears the trade.
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Midday desk cycle
- Runs on
- xAI Grok
- Tools it may use
- Position and risk review
046SentimentTrading-desk analyst covering market sentiment, read from X and market data.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Midday desk cycle
- Runs on
- xAI Grok
- Tools it may use
- X
- Market data
047TechnicalTrading-desk analyst covering quotes, charts and technicals.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Midday desk cycle
- Runs on
- xAI Grok
- Tools it may use
- Quotes and charts
048TraderTurns the trading desk's analysis into concrete trade ideas for the chair to decide on.on a clock
- What it may never do
- Cannot place or cancel an order itself.
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Midday desk cycle
- Runs on
- xAI Grok
- Tools it may use
- Market stack
The research bench
5 agents, 5 running
Finds evidence, reports what people actually said, and grades its own packets.
Show the 5 agentsHide the 5 agentsCompeti, Overheard, 30 and 2 more
049CompetiWatches competitors' pricing, product and hiring pages for changes, and sends a weekly brief.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Weekly brief
- Runs on
- xAI Grok
- Tools it may use
- Watch-list pages
- Page diff
- Weekly brief
050OverheardTracks mentions of AJ's name, brand and URLs across Reddit, Hacker News, news and X.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Subscriptions and digest
- Runs on
- xAI Grok
- Tools it may use
- Hacker News
- News
- X
- Digest
05130Reports what people actually said in the last 30 days on Reddit, X, Hacker News and YouTube.on command
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- Runs on
- xAI Grok
- Tools it may use
- X
- Hacker News
- YouTube
- Web
052EveGrades the research packets the other bots produce against a fixed rubric.on command
- What it may never do
- Grades only. Never does the research she is grading.
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- Runs on
- xAI Grok
- Tools it may use
- Evaluation rubric
053OogleDeep research on marketing, competitors and history, using web search and GitHub as sources.on command
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- Runs on
- xAI Grok
- Tools it may use
- Web search and fetch
- Deep-research skill
- GitHub as a source
Personal staff
4 agents, 4 running
Chief of staff, critic, coach, and the chair of the trading desk.
Show the 4 agentsHide the 4 agentsMonie, Skeppie, Warp and 1 more
054MonieChairs AJ's trading desk, and is the only bot allowed to place a trade, through a Robinhood agentic account.on a clock
- What it may never do
- Every live entry needs AJ's tap to accept, and Risk must clear it first.
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Midday desk cycle
- Runs on
- xAI Grok
- Tools it may use
- Robinhood (Agentic account)
- Accept widgets
- Trading-desk handoffs
055SkeppieIndependent critic: reads AJ's day and pushes back on it, in a weekday digest.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Weekday digest routine
- Runs on
- xAI Grok
- Tools it may use
- Chat
- Weekday digest routine
056WarpAJ's personal chief of staff: trips, documents and his personal inbox.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Scheduled routines
- Runs on
- xAI Grok
- Tools it may use
- Personal Gmail
- Personal GitHub
- Vercel
- Browser
- Scheduled routines
057GymmieGym coach: programmes sessions, reviews lifting form from photos and video, and sets recovery rules.on command
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- Runs on
- xAI Grok
- Tools it may use
- Session programming
- Photo and video form review
Work staff
4 agents, 4 running
The work lane: weekday brief, HR drafts, brand, and build.
Show the 4 agentsHide the 4 agentsUni, Atelier, Codie and 1 more
058UniAJ's work chief of staff at Unicity: weekday brief, Friday wrap, incidents, brewing risks and meeting prep.on a clock
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- How it runs
- Weekday 9am brief, Friday wrap, incident routines
- Runs on
- xAI Grok
- Tools it may use
- Work Gmail
- Slack
- ClickUp
- Google Calendar
- Scheduled routines
059AtelierBrand, pitch and visuals: the story goes to Figma before anything gets built.on command
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- Runs on
- xAI Grok
- Tools it may use
- Figma
- Higgsfield
- ElevenLabs
060CodieImplementation engineer across AJ's work and personal codebases, through GitHub and Cursor cloud agents.on command
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- Runs on
- xAI Grok
- Tools it may use
- GitHub (work and personal repos)
- Cursor cloud agents
061PollieUnicity HR lane: hiring, compensation and personal-data questions. It drafts only.on command
- What it may never do
- Draft-only. Never sends anything itself.
- How I know
- Seen running in AJ's Grok workspace on 18 September 2026.
- Last ran
- 18 September 2026
- Runs on
- xAI Grok
- Tools it may use
- Unicity HR workspace
Department reporting
1 agent, 1 running
Checks each morning that the AI department's own reporting actually ran.
Show the 1 agentHide the 1 agentKPI Integrity Reviewer
062KPI Integrity ReviewerChecks each morning whether the AI department's KPI reporting actually ran: data freshness, deploy status, measured or carried-over numbers, then reports to AJ.on a clock
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 31 July 2026
- How it runs
- Claude cloud scheduled routine, daily 10:30 UTC, read-only, DMs AJ.
1 agent in Department reportingKPI Integrity Reviewer
HR answer bot
1 agent, 1 running
Answers employees' HR policy questions in Slack with a source on every answer.
Show the 1 agentHide the 1 agentHR Assistant (hr-answer-bot / @hr_bot)
063HR Assistant (hr-answer-bot / @hr_bot)Answers US employees' HR policy questions in Slack from the employee handbook, cites a source every time, and routes anything else to a human.on a clock
- What it made
- An internal Slack-based question bot answered employees' HR questions during a pilot running from late July to mid-September, and every answer it gives carries a source citation by design.
- How I know
- Audited against the files on AJ's machine.
- Last ran
- 17 September 2026
- How it runs
- Deployed Slack Socket Mode bot on Google Cloud Run. The project's append-only wiki log records dated merges through 2026-09-17, each of which redeploys a new Cloud Run revision via the repo's build trigger.
- Runs on
- Anthropic Claude, Sonnet 5
- Tools it may use
- Slack Socket Mode (Bolt)
- Anthropic SDK (citations)
- Google Drive corpus sync
- Document AI (PDF/DOCX parsing)
1 agent in HR answer botHR Assistant (hr-answer-bot / @hr_bot)
Storefront reviewers
5 agents, 0 running
Reads changes to a global storefront before they are allowed near a pull request.
Show the 5 agentsHide the 5 agentscode-reviewer, goal-verifier, pre-pr and 2 more
064code-reviewerReviews code changes in Unicity's Shop2 storefront for quality, conventions and correctness before a person reviews them.built
- How I know
- Audited against the files on AJ's machine.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Grep
- Glob
- Bash
- Write
- Edit
065goal-verifierRe-runs every acceptance check itself in a fresh context instead of trusting the implementer's evidence, then writes a pass or fail verdict.built
- What I taught it
Wrongly approving bad work is the worst outcome; failing a borderline change is cheaper.A false PASS is the worst possible outcome
- How it is checked
- This agent is the check: it is the only agent allowed to write the PASS/FAIL verdict into the goal-plan ledger, and it re-runs the deterministic checks itself (format/lint, build, git diff) instead of trusting the implementer's pasted evidence.
- How I know
- Audited against the files on AJ's machine.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Grep
- Glob
- Bash
- Edit
- WebFetch
066pre-prChecks lint, types, build and documentation freshness before a pull request on the Shop2 storefront is opened.built
- How it is checked
- Runs lint/format, build, a convention scan and a doc-freshness scan itself and prints a READY / NOT READY verdict.
- How I know
- Audited against the files on AJ's machine.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Grep
- Glob
- Bash
067quick-fixHandles small isolated fixes under about ten lines, typos, one-line bugs, bad imports, without a full planning pass.built
- What I taught it
When unsure, stop and ask instead of guessing.If you're unsure about the fix, STOP and ask rather than guessing
- How it is checked
- Runs `npm run formatAndLint` itself after the edit and reports passed/failed.
- How I know
- Audited against the files on AJ's machine.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Edit
- Grep
- Glob
- Bash
068researcherExplores the Shop2 storefront codebase to find patterns, locate files and explain the architecture before a feature is planned.built
- How I know
- Audited against the files on AJ's machine.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Grep
- Glob
Idea appraisal
4 agents, 0 running
Turns a one-line idea into sourced evidence, a critic's attack, and a go or no-go.
Show the 4 agentsHide the 4 agentsdisc-researcher, disc-critic, disc-designer and 1 more
069disc-criticAttacks the research's weakest assumptions, checks the cited sources are real, hunts counter-evidence, and returns a go / no-go verdict.built
- What I taught it
Stopping a bad idea early counts as the process working.A killed idea early is a success for this process, not a failure.
- How it is checked
- pipe-grader scores it against its written rubric; it works blind, receiving file paths only and never the researcher's reasoning or confidence.
- How I know
- Audited against the files on AJ's machine.
- Runs on
- Anthropic Claude
- Tools it may use
- Read
- Grep
- Glob
- Write
- WebSearch
- WebFetch
- ToolSearch
070disc-designerBuilds a clickable HTML prototype in the right design system when an idea needs a user interface, with borrowed patterns sourced.built
- How it is checked
- pipe-grader scores it against its written rubric; the prototype must open standalone with no console errors, and every borrowed pattern must be listed with its source.
- How I know
- Audited against the files on AJ's machine.
- Runs on
- Anthropic Claude, Opus
- Tools it may use
- Read
- Write
- Edit
- Grep
- Glob
- WebSearch
- WebFetch
- ToolSearch
071disc-presenterWrites the stakeholder summary page for an idea: sourced numbers split into proven, built but unproven, and dependent on someone else.built
- What I taught it
Only label something 'verified' if it was actually checked.Never move something into "working now (verified)" that no one has verified.
- How it is checked
- pipe-grader scores it against its written rubric, and it scores its own prose with the stop-slop checklist: below 35/50 it must revise the page and score again, and may not return under 35.
- How I know
- Audited against the files on AJ's machine.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Write
- Edit
- Grep
- Glob
072disc-researcherTurns a one-line business idea into cited competitor evidence, a recommended approach, success metrics, an effort estimate and kill criteria.built
- What I taught it
Every fact and figure must be real, never made up.Never invent a number, a baseline, a competitor, or a product feature.
- How it is checked
- pipe-grader scores it against its written rubric, and disc-critic then attacks the same receipt with the stated job of trying to kill the idea.
- How I know
- Audited against the files on AJ's machine.
- Runs on
- Anthropic Claude, Sonnet
- Tools it may use
- Read
- Grep
- Glob
- Bash
- WebSearch
- WebFetch
- ToolSearch
Growth pipeline
3 agents, 0 running
Pulls app analytics and feedback, ranks what to build next, and builds one.
Show the 3 agentsHide the 3 agentsBuilder (growth pipeline), Gatherer (growth pipeline), Synthesizer (growth pipeline)
073Builder (growth pipeline)Builds one approved feature for The Method app on its own branch, runs checks, updates docs, and reports the commit to ClickUp and Slack.built
- How it is checked
- Runs lint, a TypeScript typecheck (`npx tsc, noEmit`) and lint:expo itself after implementing and must fix any failure before proceeding.
- How I know
- Audited against the files on AJ's machine.
- Tools it may use
- ClickUp (read task)
- ClickUp (update task)
074Gatherer (growth pipeline)Pulls The Method app's Mixpanel analytics, Supabase feedback rows and Slack wishlist ideas into one structured file per cycle.built
- How I know
- Audited against the files on AJ's machine.
- Tools it may use
- Mixpanel (via MCP)
- Supabase (SQL via MCP)
- Slack (read channel)
075Synthesizer (growth pipeline)Cross-references the gathered analytics, feedback and ideas, and ranks the features most likely to move the chosen growth metric.built
- How it is checked
- Runs its own Reality Check step before finalizing: each proposal must be actionable, scoped, measurable, and aligned to the success metric.
- How I know
- Audited against the files on AJ's machine.
3 agents in Growth pipelineBuilder (growth pipeline)Gatherer (growth pipeline)Synthesizer (growth pipeline)
House rules
4 of 11 are enforced by code
Databases are read-only by default
Never run a database write without the human explicitly approving that exact change first.
Enforced by a hook that stops the call and makes the human approve itPersonal and work accounts never mix
Keep personal and work identities separate on every service; a guard blocks the wrong one automatically.
Enforced by a hook that blocks the actionName the model on every call
Always set the model explicitly per agent call; the strongest model is reserved for the hardest judgment seats.
Enforced by a hook that blocks the actionNothing goes out unscored
Score outbound writing on five clarity dimensions and revise anything below the pass threshold before sending.
Enforced by a hook that fires before every outbound send and forces the checkBe a critic, not a yes-man
Stress-test ideas and lead with what's wrong before offering any praise.
A rule I followPlain language, three honesty buckets
Explain work in plain terms and sort progress into working, unproven, and dependent-on-others, honestly.
A rule I followPipelines run only when invited
Never start the multi-agent pipeline on an ordinary request; recommend it and wait for explicit approval.
A rule I followA second model audits the plan
Run an adversarial Claude-versus-Codex debate on a plan and resolve blockers before building starts.
A rule I followTests first, then the fix
Write the failing test before writing the fix, and never edit a test just to make it pass.
A rule I followExternal code stays external
Never install internal tooling, tracking, or process into a third-party repo without explicit case-by-case approval.
A rule I followOne writer at a time
Never let two agents edit the same repository at once unless they touch completely separate files.
A rule I followHard limits on 5 agents
- Risk, on the trading desk. Holds a veto: the chair is blocked until Risk clears the trade.
- Trader, on the trading desk. Cannot place or cancel an order itself.
- Eve, on the research bench. Grades only. Never does the research she is grading.
- Monie, on personal staff. Every live entry needs AJ's tap to accept, and Risk must clear it first.
- Pollie, on work staff. Draft-only. Never sends anything itself.
Two apps in the stores
Live in the stores
The Method by Unicity
The daily-practice companion for graduates of The Method Seminar: goals, vision, breathwork and streaks, in nine languages.
Designed and built solo by AJ Pardilla, with AI agents as the engineering team. Published by Unicity.
In the week of 31 August 2026: 808 people used The Method, 466 a day, 517 of them practised, 4,726 sessions.
58% of weekly users open the app on any given day. Average daily users grew from 75 in April to 475 in September, with a peak of 493 on 9 August.
New members still practising, by day
The Method Weekly Pulse, production analytics in Mixpanel, project 4001739, generated 11 September 2026. Small internal and testing traffic may be included.
The pipeline behind it
Eight steps, and where each one really runs
Cloud agents that take a feature from a Slack message to a reviewed, device-tested build AJ approves from his phone. About ten dollars a month.
Between 5 and 13 September 2026, three Slack requests were planned, coded and independently reviewed by agents in the cloud. One came back as a build AJ approved from his phone, and the cloud recorded that approval and advanced the ticket by itself.
Two human gates are built in: I approve the plan, and I approve the preview build before anything ships.
- AJ posts a request in Slack.in the cloud
- A Chief of Staff agent scopes it.in the cloud
- Researcher, Planner and Evaluator agents write and score a plan.in the cloud
- AJ approves in Slack. First human gate.in the cloud
- An Engineer agent writes code. An independent Reviewer checks it.in the cloud
- QA agents write device tests. A second Mac runs them with the screen locked.on the test Mac, with nobody watching
- A preview build publishes and a QR code posts to Slack. Second human gate.on my machine
- A pull request opens, a human merges, and store submission stays manual.by hand, by design
Receipts
Five, each with the thing you would check
- Shipped
- A pipeline of agents took a real feature from request to a merged, deployed, health-checked change. I reviewed and decided. I did not write the code.
- PR #29, commit 8060517. Deployed 6 September 2026.
- Measured
- An internal registry of agents and projects, with a test suite above 95% statement coverage. Its dashboard prints “not measured” where no data exists.
- Commit 8378a9f, 9 July 2026. 428 automated tests.
- Cited
- An HR question bot in Slack answers from the approved policy documents. Every answer carries a source. When it cannot cite one, it refuses.
- Seven-week pilot. 54 cited answers.
- Gated
- The full pipeline runs only on my yes. A written rule says which jobs are big enough to earn it, and the agents must ask first and name the cost.
- Standing rule since 12 September 2026.
- Running
- One always-on agent runs a collect, synthesise and brief cycle about every half hour, and leaves a dated receipt for each one.
- The pccd daemon. 35 dated runs on 18 September 2026.
How I got here
In order
01Design
02Marketing
03Ecommerce and payments
04Product
05AI
Nutrigold. Studies Weekly. Ridgway. Unicity International.
Unicity International, 2022 to now
| Checkout approval, EU and Japan | 64% | to | 94% |
|---|---|---|---|
| Product launches per year, counted by market | 3 | to | 40 |
| Fraud rate on those checkouts | about 30% | to | under 1% |
These three are from my own record of the work.
Off the clock
Elsewhere
Father to Astra. Husband to Mariko.
About ten countries a year. Space and technology are the two subjects I never get tired of reading about.
How this site was made
By the agents it describes
I directed agents to build this page. One set swept my machine and my Grok workspace and listed every agent it could find. A second set audited the first and opened the files behind each claim, so each of the 75 agents on this page traces to a real file or a running bot.
Four designs were then built from the same audited file, and three judges scored them. This page is the merge they asked for. Every number on it is computed from the audited file when the page is built, so it cannot drift from the data.
The thread ends here.
If any of this is useful to you, I would like to hear it.
Every number on this page was counted from the audited file when the page was built. 75 agents in the register, 63 of them running.
Start a conversationRegister current at 18 September 2026
On LinkedIn