Corporate event

The list shows the knowledge items — glossary, product, policy, tone of voice and procedure — with scope, weight, size and whether active. At the top is the usage of the limits (items, characters and calls per day) and, collapsed, the preview of what Tenkai receives, capabilities, external sources, the usage log and verified answers.

Todo 👎 com comentário na conversa, toda pergunta que caiu em "não encontrei" e toda rejeição no Conciliador viram um item aqui. Você aprova dizendo o que ele é: um SINÔNIMO (entra na tela escolhida e o roteador passa a entender a palavra), uma REGRA determinística (fornecedor → conta, usada antes do agente) ou um CASO de avaliação (o harness passa a cobrar). Aprovado muda a próxima resposta; revogar desfaz o efeito. O contador "aprendi N" é o número de aprovados no mês.

Informe o bucket (S3 ou compatível — GCS pela API interoperável, MinIO), o prefixo, a região e as credenciais; elas ficam cifradas. Toda noite o Tenka manda o que mudou desde a última rodada, uma pasta por entidade, em CSV comprimido, com um manifesto do que saiu. Power BI, Metabase e Athena leem direto do bucket; ninguém precisa de SQL no Tenka. As regras de linha da sua empresa e o Ver Valores de quem configurou valem na exportação.

When Tenkai uses an item from this record, it says which one it used. Context that changes the answer without showing up is worse than no context: whoever reads it has no way of knowing where the number came from, and no way of fixing the source when it's wrong.

On, off and "never decided". The third is the factory default: until you choose, the platform default applies — and the screen shows it with that word, not as if it were your choice. That way, when a new capability arrives, you know it came from outside and not that someone on your team turned it on.

It's stored encrypted (AES-256-GCM) and isolated in your account. Once saved, the field only shows that a credential is stored — to change it, you type the new one. There's no button to reveal it: a secret the screen can show is a secret that any screenshot, any shared session and any screen capture can also show.

Each account has a limit on context items, total size and calls to external sources per day. The screen shows consumption against the limit before you hit it. When the size limit gets tight, the highest-priority items go in first — that's what the order is for, not decoration.

On the record, type, title and content are required: answers cite the item by its title, and an empty item only takes space. The item limit is enforced when adding — with the account at the limit, delete or deactivate one before adding another. The scope, when filled, restricts the item to a part of the system; empty applies to the whole account.

In external sources (MCP), the credential is INPUT only: the screen never shows it back, it only says whether one is stored. To change it, type the new one and save; to erase it, use the key on the row. Deleting a context item removes it for good (there is no trash) — deactivate instead of deleting if you just want to pause it.

The screen's help explains the SYSTEM — what a profit center is, what the accrual column is for. What you write here explains your COMPANY: that "MP" means raw material, that spools are sold by the kilo, that the customer is called a partner. One is the same for everyone; the other is yours alone, and it's what makes the answer sound like someone who works here.

Whoever already edits the Company Settings. Whoever administers the account through the Access and Approval limits screens can SEE, to check and explain, but not write: the text here becomes an instruction for the whole company's assistant.

When you approve a curation item as a synonym, it goes into your company's glossary — the same one you see in Tenkai Context — and Tenkai starts understanding the word your way. No other account is affected. Revoking removes the synonym from the glossary.

In Parquet: one file per subject per night, in folders by date, with each column in its proper type (text, number, date, yes/no), plus a manifest of what was sent. Power BI, Fabric, BigQuery and Databricks read it directly, with no decimal-comma fixing. Money values arrive empty if whoever configured the destination cannot see values. If you already built your load on the previous compressed CSV, set the parameter Warehouse: file format to CSV.