Question 1

What is PortalKinetic?

Accepted Answer

PortalKinetic is the Relief Operating System for overloaded professionals: clear your head, see what matters, and take one next step. It is not professional care, does not label people, and is not employee monitoring. It helps a person move from overload to relief, from relief to clarity, and from clarity to one next move. The core law is simple: show one useful next action and hide everything else until needed.

Question 2

What is PortalKinetic in one sentence?

Accepted Answer

PortalKinetic is the Relief Operating System for overloaded professionals: clear your head, see what matters, and take one next step. It helps people clear mental clutter, regain clarity, and find one next move without adding to the load.

Question 3

What are the operating laws behind the product?

Accepted Answer

Four laws shape the product and the enterprise boundary. Show one useful next action and hide everything else until needed. Reduce what the user is holding instead of adding new overhead. Keep the individual space private without exception. Give the organization patterns, not people, through aggregate and cohort-safe reporting only.

Question 4

Is PortalKinetic employee surveillance?

Accepted Answer

No. PortalKinetic is not surveillance. The individual workspace stays private, and organization reporting is aggregate and cohort-safe. Employers do not see private tasks, Mental Unload text, journal content, individual reset history, raw recovery paths, or per-user output exhaust.

Question 5

What is PortalKinetic not?

Accepted Answer

It is not professional care, not employee monitoring, and not an output tracker. The system exists to protect capacity, not extract output.

Question 6

What does the first useful minute feel like?

Accepted Answer

The product should feel lighter immediately. Instead of a crowded dashboard, the user starts with a simple state door such as 'I'm stuck' or 'I need quiet.' PortalKinetic shows one useful next action, explains why it fits, gives a short time expectation, offers a fallback, and lets the user stop cleanly. The goal is relief first, then one next move.

Question 7

What individual signals are available to enterprise admins?

Accepted Answer

The employer-visible reporting plane does not receive keystroke timing, typing cadence, focus-switch signals, mouse dynamics, gaze tracking, screen monitoring, raw activity trails, private content, individual scores, or per-user output exhaust. Those signals are not available to managers and are not returned in buyer-facing telemetry.

Question 8

Can managers export capacity signals to HR systems?

Accepted Answer

No. Predictive capacity signals are not exported to HRIS, compensation, promotion, discipline, or termination systems. Enterprise value comes from aggregate overload and recovery patterns, not performance management.

Question 9

What should an enterprise pilot measure?

Accepted Answer

Use proof metrics that match the product boundary and are explicitly instrumented for the pilot: activation-to-first-next-move, relief_tap_to_first_stage_ms, weekly meaningful actions, cohort retention, cohort completion patterns, security-questionnaire pass rate, and support-ticket volume where explicitly instrumented. Do not claim output lift, exhaustion reduction, or 6.8x engagement unless a named cohort has approved instrumentation.

Question 10

What makes this infrastructure instead of another employee benefit?

Accepted Answer

The repeatable loop sits inside work: clear mental clutter, choose one next move, reset when overloaded, and report only aggregate adoption and outcome patterns. The moat is trusted restart patterns and privacy-preserving aggregate intelligence, not manager dashboards.

Question 11

Can individual capacity signals be exported to HR or performance systems?

Accepted Answer

No. Individual capacity signals are never exported to HRIS, compensation, promotion, discipline, or performance-management systems. Enterprise value comes from aggregate overload and recovery patterns at the cohort level, not from individual-level performance scoring. The boundary is architectural: individual states are stored in a form the employer plane cannot read.

Question 12

What is the shortest way to explain this to a skeptical employee?

Accepted Answer

PortalKinetic shows aggregate overload and recovery patterns without exposing the people carrying them. The individual workspace belongs to the employee. The organization only sees cohort-safe patterns - never names, scores, or raw content.

Question 13

Why is the privacy boundary treated like a product law?

Accepted Answer

Because trust determines whether people use the product honestly. The moment an employee thinks private notes or reset patterns can flow to a manager, the support loop breaks. The boundary is enforced in the data shape: the employer-visible reporting plane cannot return identity, private content, individual history, or a comparable score.

Question 14

Can a manager use PortalKinetic to rank or compare employees?

Accepted Answer

No - and this is architectural, not a policy choice. A leaderboard requires stable individual identifiers in telemetry, individual activity history, task or output content, and comparable scores. The employer-visible reporting plane prevents ranking because it never receives those ingredients.

Question 15

What does the enterprise admin dashboard actually show?

Accepted Answer

Aggregate sessions started, aggregate sessions completed, aggregate duration, aggregate completion rate, meeting-recovery-to-focus rate, weekly trend lines, and aggregate helpfulness signals — all at the cohort level with minimum group sizes enforced before display. It does not show who is overloaded, who completed which relief path, individual reset history, private intention text, or anything that maps a pattern back to a named person.

Question 16

Can you give simple examples of what admins can and cannot answer?

Accepted Answer

Yes. The employer-visible reporting plane can answer: Is the support layer being adopted? Are aggregate sessions starting and completing? Are cohorts returning over D7/D30 windows? It cannot answer: What did Sarah write today? Who is struggling? Who focused more than whom? Who should be ranked, promoted, punished, or managed differently?

Question 17

What does the enterprise telemetry payload contain?

Accepted Answer

The buyer-facing payload contains eventType, eventCount, uniqueUsers, eventDay, period, and privacy metadata such as min_unique_users and suppressed_small_cohorts. It intentionally excludes user_id, email, task_title, mental_unload_text, journal_content, individual_score, raw payload, and sub-day timestamps.

Question 18

How should a CTO explain the implementation at a high level?

Accepted Answer

There are two planes. The employee plane stores the private relief workspace. The employer-visible reporting plane receives only aggregate, cohort-safe reporting rows after suppression rules run. The telemetry contract defines allowed fields, the excluded-fields matrix blocks identity and private content, and regression tests guard against user-level reporting entering buyer-facing reports.

Question 19

What should a buyer ask us to prove during review?

Accepted Answer

Ask for the telemetry contract, excluded-fields matrix, cohort suppression rule, example payload, and regression tests. The clean anti-surveillance standard is: if the employer-visible reporting plane cannot return identity, private content, individual history, or a comparable score, then it cannot support the leaderboard buyers are worried about.

Question 20

Can we use a Customer-Controlled Aggregate Store?

Accepted Answer

[SHIPPED: customer-controlled aggregate routing, encrypted secret refs, routing profiles, and CCDP drift tests] Yes, for aggregate reporting under a signed enterprise agreement. PortalKinetic supports a Customer-Controlled Aggregate Store so your team can control residency, retention, auditability, approved cohort dimensions, admin roles, and key management for aggregate data. That option does not give the organization access to private notes, Mental Unload content, private next moves, individual relief history, or raw user-level event streams.

Question 21

What does the organization actually see?

Accepted Answer

The organization sees aggregate, cohort-safe support patterns such as relief sessions started, next moves selected, cohort completion rate, adoption trend over time, time to first next move where explicitly instrumented, and general support-layer usage. Small cohorts are suppressed before they become a buyer-facing report.

Question 22

What does the organization never see?

Accepted Answer

The organization never sees private notes, Mental Unload text, journal content, private task titles, individual reset history, individual scores, employee rankings, keystroke timing, mouse tracking, screen monitoring, gaze tracking, raw telemetry payloads, or sub-day activity timelines. That boundary is how PortalKinetic avoids becoming bossware.

Question 23

What prevents a small pilot from turning into one-person reporting?

Accepted Answer

The reporting contract stays aggregate even in a small rollout. Rows below min_unique_users are suppressed before display, buyer-facing trends stay at the cohort and day level, and the payload excludes stable employee identifiers, private content, individual history, and sub-day timelines. That means a manager cannot drill from team proof into one person's private state.

Question 24

Why will employees actually use it?

Accepted Answer

Because trust is the adoption engine. If employees think a manager can see their private state, they will avoid the tool or perform for it. PortalKinetic keeps the individual workspace private so people can use the support layer honestly, and that honest usage is what makes the aggregate organization pattern meaningful.

Privacy-safe answers for enterprise review.

Need the full trust path?

Elastic

Privacy-safe answers for enterprise review.

Need the full trust path?