Each program has its own rules.

Memory is organized by unit and by program, and permission defines the scope of each answer. The agent answers by the rules of the asker's program, with the source cited.

Who answers the student, the agent or the registry?

The agent answers with the source cited when there is a rule in force. The sensitive case escalates to a person, who receives the conversation history ready.

What about student data?

Data in Brazil, in compliance with the LGPD. Tenant isolation, permissions inherited per person and per source, and an audit trail for every read.

Industry · Education & Higher Education · schema_pack: 6 types

The academic rule that holds today, with its source.

Current regulations with source in student service, and research projects with continuity across semesters and advisors.

Scenario

How context circulates when ValorBrain is in the flow.

01
The regulations stay versioned, with validity and an owner.
02
The agent answers the student's question citing the resolution and the date.
03
Permission applies before the prompt: the agent sees only what the role of whoever is serving allows.
04
The research project accumulates decisions, context data, and sources.
05
The new advisee, or the support agent, starts from the accumulated context.
06
The semester change doesn't reset the project.
07
The new resolution supersedes the previous one without erasing history.
08
The service agents start receiving the version in force.
09
Conflict between resolutions is flagged for human review.

Schema pack

Schema pack types: regulamento + resolução + projeto de pesquisa + política + atendimento + auditoria

The same mechanism, applied here

Next step

Less starting over. More continuity

Bring a real project. In one conversation we map where context gets lost between the people and agents on your team, and where to start.