Chapter 1 · Meet BasilAOS — Your New Work Partner1.8 App

1.8.2 Base: Data the Agent Can Query and Write Back

The previous lesson put files in Library. But work also holds a second kind of content: inventory tables, order records, customer lists, sales detail.

Those can live as Excel files in Library too. But then the agent can only read them, not act on them — adding a record, changing a status, filtering ten rows to a condition all need a different carrier.

Base is built for that kind of content.

What Base Is

Base is a structured-data page embedded in AOS Work and belongs to the App resource type. It manages tables, records, and fields, and the agent can both query it and write back to it.

The test

Does this content need to be queried, filtered, and written back? Then Base. If it only needs to be read, Library is enough.

How It Divides the Job With a Spreadsheet

DimensionSpreadsheet file (in Library)Base
What the agent can doRead the contentQuery, filter, write, update
Multi-person workDepends on file versionsOne dataset, several people at once
PresentationA single sheetTable, Assets, Gallery, and Kanban views
PermissionsFile levelRole level

They are not substitutes: a one-off analysis is more direct in a file; data that is maintained, queried, and written over time belongs in Base.

Two Ways to Use It

Query: one sentence instead of scrolling a sheet

Look at the product table and list every item with stock below 200.

The agent queries the table, returns the result, and embeds a live preview in the conversation. That preview is read-only; open Base from the sidebar for the full page.

Write: land the result in the table

The reason a flow like "read the email → extract fields → write to a table" can run end to end is that Base accepts writes.

Enabling It: The Same Flow as Library

For adding and authorizing the app, see AOS Work: Base. To prepare an exercise table and check written records, see the AOS Studio demos in Tables and Records.

Base and Library are both embedded Apps, so the path is identical:

  1. Open 【Explore】 → 【Apps】.
  2. Find Base, click 【Add】, and enable it.
  3. Follow the authorization prompt; an existing Library authorization can be reused.

The apps are added separately and share authorization. Once complete, a Base entry appears in the left sidebar.

Exercise: Query, Update and Read Back

After adding and authorizing Base, prepare a Base named Tutorial Inventory and create its Products table. Add SKU (text, product code), Stock (number, inventory quantity), and Status (text, handling status). Enter the three records below. Open means not yet handled; the later Reorder status means replenishment is needed:

SKUStockStatus
DEMO-101120Open
DEMO-102260Open
DEMO-10380Open

Open 【New Chat】, enter the request below, select 【Base】 through 【Add context】 → 【Choose apps】, and send:

Query Base Tutorial Inventory / Products for Stock below 200. Return SKU, Stock and Status. Do not update records.

Only DEMO-101 and DEMO-103 should match. In the same conversation, enter the follow-up below, select 【Base】 again, and send it to update their status by SKU:

Set Status to Reorder for SKU DEMO-101 and DEMO-103 in Tutorial Inventory / Products. Keep Stock and all other records unchanged.

Then enter the follow-up below, select 【Base】, and send it to read every record again:

Read all three records again from Tutorial Inventory / Products. Return SKU, Stock and Status to verify the update.

Acceptance: there are still 3 records. DEMO-101 and DEMO-103 have Status set to Reorder; DEMO-102 remains Open. Stock stays at 120, 260, and 80 respectively. You can also open Base from the sidebar and compare the saved values in Products.

Permission Roles

RoleWhat it can do
OwnerFull control, including permission settings
AdminRead, edit, and manage the data in Base
ReaderRead-only access

Permissions are assigned by role, so the same data can be shared with a team for reading or collaborative editing while the boundary stays clear.

When Base, When Library

ScenarioLibraryBase
Read a contract and compare versionsYes—
Read a PDF and translate itYes—
Extract fields from email into a table—Yes
Count stock and find slow-moving SKUs—Yes

In one line: Library handles reading; Base handles querying and writing. They usually work together — files in Library, the structured result in Base.

Summary

Base makes data something you can act on, not just look at.

That completes the four resource types. The next lesson returns to the two context mechanisms: Memory and the workspace.