Knowledge We're going. Come say hi.

Catch drift on every scan.

83 checks, in the box

83 best-practice scan definitions ship out of the box — across upgradeability, performance, security, user experience, and maintainability. Every change Phyllis makes is held to the same standard a senior ServiceNow architect would apply, automatically.

Phyllis Monitor workspace preview

Loop

Phyllis monitors every build

Every dev task Phyllis runs ends with an Instance Scan — Phyllis self-heals what's fixable, and what isn't becomes a sprint-ready story. The work Phyllis ships isn't the work that breaks production.

Monitor, @ for context, / for commands
acmetest Monitor claude-opus-4-7

Remediate

Findings Phyllis can fix, Phyllis fixes

Phyllis resolves findings — diagnose, suggest the fix, and on approval Phyllis stages the remediation update set, scoped correctly and ready for sign-off. You approve the path, Phyllis ships it.

Remediate · GlideRecord in loop acmetest
Finding context loaded
Artifact pulled · incident_assign
Refactor ready · GlideAggregate diff
ATF regression · 12/12 passed
Peer review · approved
Scan Results
Scan Run Severity
All Run = acmetest_250420 State = open
Check Severity Artifact
GlideRecord in loop High incident_assign
Hardcoded sys_id Medium vip_priority
Missing ACL Critical sc_cat_item_laptop

Scan

Update set or full instance — your call

Scan a specific update set before it promotes when you want a focused gate, or the full instance when you need a sweep. Same definitions, same depth, different blast radius.

Phyllis AI
Scopes the scan — update set before promotion, or full instance for a sweep.
ServiceNow Live
Instance Scan + ATF after every change lands in prod.
Automated Test passed
Instance Scan clean

Triage

Findings become sprint-ready stories

What Phyllis can't auto-fix doesn't sit in a backlog list. Phyllis scopes each finding into a user story with severity, owner, and acceptance criteria — ready to drop into the next sprint.

Policy.v14 Owner · CAB
Approvals required
  • Platform Lead
  • Security
  • Change Manager
Backlog Story STRY-0251

Story

Story Details

From finding GlideRecord in loop
Owner platform_team · incident_assign
Sprint READY
scan_run:acmetest_250420 acceptance · 3 criteria sprint:S-2026-09 · queued
Every finding sized and sprint-ready

Estate

Every instance, from one place

Connect dev, test, prod, and partner instances. Run scans against any of them on demand, with scope separated per instance and the same best-practice definitions applied across the estate.

dev
test
uat
prod

Implement now.