Overview

Loading…

Today

–

questions checked

Refused

–

each shown the clause and a way forward

Warnings

–

from rules still in warning mode

People

–

asked something today

What needs you

Close to a line one question away, last 7 days

Last 14 days checked refused

14 days agotoday

Refusals by clause 30 days

Coverage

Policy

Your handbook, as rules. Each starts in warning mode, which shows what would be refused; enforce when you're confident.

Re-draft from handbook Add a rule

Last 7 days

requests checked

Refused

every one shown the clause

Would refuse

across 3 rules still in warning

People

with activity

Rules Toggle = enforce. Sparkline = daily hits, last 14 days.

Rule	Type	14 days	Tests	Enforce
Loading rules from coc.yaml…

Flip 7.2 to enforce? Last week 31 requests by 9 people would have been refused. 7 of them from Recruiting, who pull candidate lists daily. Suggested: add a review-session exception for Recruiting before enforcing. See the 31 →

Handbook & examples mock

Every rule carries its own examples. A rule that fails its examples can't be enforced.

Upload new handbook version Run all tests

Employee Handbook v4.2 uploaded 12 Aug · 41 pages

Clause	Status
7.1 Personnel × budget × rota	Rule
7.2 Bulk lists	Rule
7.3 Legal hold	Rule
7.4 Respect and harassment	Not enforceable here
7.5 CRM × compensation	Rule
7.6 Timesheet comparison	Rule
7.7 Expense claims within 30 days	Not enforceable here
7.8 Absence × promotion	Rule
7.9 Board materials	Rule

Two clauses can't be enforced at a data proxy (tone, deadlines). They stay in the handbook; they're just not Aggrete's job.

Tests for 7.1 4 examples · all pass

Example	Expect	Result
Manager sees budget, then people, then asks for the rota on the same six	Refuse	✓
Budget and rota only (two of three)	Allow	✓
All three domains, no shared people	Allow	✓
All three, but under a review session	Allow · logged	✓

Add an example in plain words; Aggrete turns it into a test. Add example →

Decisions

One line per question an assistant asked on someone's behalf. Open one to read what happened.

Send to Splunk Export CSV Evidence pack (PDF)

Today7 daysAllRefused only

Time	Person	Asked for	Stage	Decision
Loading audit.jsonl…

Select a decision

What happened, in plain words, appears here.

Exceptions mock

Sanctioned exceptions. A session lasts four hours; every retrieval under it is logged against the reason given.

Slack approvals: on

Waiting for HR Privacy 2 open

M. Okafor · Engineering Manager, Platform

"Q4 workforce planning with Finance. I need the on-call coverage against the backfill list to size the hiring ask."

Requested 14:12 · would lift rule 7.1 for 4h · 3 connectors · logged

Decline Approve 4h

R. Adeyemi · Recruiting Lead

"Weekly candidate pipeline export for the hiring committee."

Requested 09:30 · would lift rule 7.2 for 4h · recurring? Make it a standing exception →

Decline Approve 4h

Active sessions 1

A. Reyes · Compensation Analyst

"Annual pay-equity review, board pack."

Approved by K. Müller 10:58 · expires 14:58 · 14 retrievals logged · rule 7.5

View retrievals End early

Approvals also land in #hr-privacy on Slack with the same two buttons. Every decision here is itself an audit line.

People mock

Rules count people, so every connector's identifier must resolve to one person. Directory: Google Workspace.

Re-sync directory Resolve unlinked

People

1,842

from the directory

Identifiers linked

5,509

across 6 connectors

Unlinked

seen in results, no person yet

Coverage

99.9%

of identifiers seen this week

Needs attention identifiers that appeared in results but don't map to a person. Rules can't count them

Identifier	Seen in	Best match
WD-00417	Workday · 12 results	DR Dev Rao d.rao@corpE-1074	Link
U03KX9F2	Slack · 4 results	? No confident match display name "frank w"	Search directory
003Dn00000Q7	Salesforce · 1 result	Probably a customer contact, not an employee	Mark external

Example · one person, six identifiers

Adaeze Nwosu · SRE II, Platform

a.nwosu@corpWorkday WD-00391HRIS E-1041Slack U02H7QKJira anwosuDrive owner

Because these six resolve to one person, "6 people" in the 14:07 refusal really means six people. Not six emails and six employee numbers.

Test a new handbook

Upload a draft of next year's handbook and see what it would have done over the last ninety days of real questions. Nothing is enforced.

Upload handbook (PDF or Word)Load current rules Compare with today

Draft rules from your upload, or paste in Advanced

Impact not run yet

Run a replay to see, rule by rule, how many requests would be refused or warned, by whom, compared with today's policy.

Close to a line

People who are one question away from something the handbook forbids. Nobody here has been refused; this is the approach, not the event.

Refresh

Person	Rule	Distance	Already holds	Would complete it	Shared people	Nudge shown
Loading…

Nobody here has been refused. This is the approach, not the event. The nudge text is what the assistant can show the person before they ask the next question.

How exceptions are used

Review sessions learn from how they are used. Recurring ones can become standing roles; ones used outside their purpose narrow themselves.

Leases · 90 days

–

granted review sessions

Retrievals under lease

–

every one logged against its purpose

Recurring

–

candidates for a standing role

Mismatches

–

used outside their purpose

Recurring: propose a standing role

Loading…

Mismatches: narrow the lease

Loading…

After a grievance

After a grievance, does the named manager's assistant start pulling records about the complainant more than it used to? Nothing is blocked. HR sees the pattern.

Manager	Complainant	Case	Before	Since filing	Where they looked	Level	Note
Loading…

Baseline is the same manager's retrievals about the same person in the 30 days before the filing. Levels compare per-day rates, so a manager who always looked will not be flagged for continuing to.

Connectors mock

What each system's tools count as, in the policy's words.

Add connector

Connector	Tools	Counts as	Identity field	Status
Workday	hr__*	hr-personnel	employee_id, email	Fenced to Aggrete
Finance (Anaplan)	finance__budget_*	finance-comp	owner_email	Fenced to Aggrete
PagerDuty	ops__*	ops-rota	user.email	Fenced to Aggrete
Google Drive	drive__*	timesheets legal-hold by folder	owners[].email	Fenced to Aggrete
Salesforce	crm__*	crm-accounts	OwnerId → directory	Reachable directly. Fence it

"Fenced" means the connector accepts traffic only from Aggrete. Until it does, a person can bypass the rules by connecting an assistant to it directly.