Tama / Private release
Knowledge and permissions - Tama
Keep distribution, knowledge review and approval separate.
Instruction, knowledge or folder
An instruction tells an agent how to work. Knowledge is reference material. A folder organizes items. Pages are versioned and can inherit assignment and delivery settings from their parent.
Delivery is not knowledge review
An instruction can have a newer version that an agent has not received. Separately, a knowledge item may need review because a source changed. Timing colors show delivery rules, not proof that an agent read or understood the content.
Dependencies and memory
Choose dependencies explicitly; a folder hierarchy alone does not create them. Changes to tracked pages or memory can mark dependent items for review. A review records the source versions and the reason for the decision.
Pipeline and outdated selections
The page editor can capture selected text, its revision and nearby context as an outdated mark. Pipeline keeps the evidence apart from the proposal. Applying a change creates a revision; confirming validity records evidence without rewriting the content.
Review timing
The service checks knowledge review dates in the background. Automatic analysis requires permission and respects its daily run limit. A review date is not a promise to start at an exact second.
Grants
A human manages approvals for the applicable task and permission scope. Instructions and knowledge do not create permission to access arbitrary data. A default Tama agent is available. You may grant automatic validity confirmation for specified knowledge; changing its content still requires your decision.
Updated September 24, 2026