Built-In Types

Nenu defines six intrinsic type keywords: string, number, bool, time, image, and file.
App Marché supplies runtime contracts such as Request, Response, and the platform-owned User type.
Applications consume platform-owned types but never redeclare them or guess their undocumented fields.

Intrinsic Type Keywords

Type	Represents	Room example
`string`	Text.	`"Internet"`
`number`	Integer or decimal numeric values.	`72.50`
`bool`	Exactly true or false.	`false`
`time`	A timestamp value.	`expense.createdAt`
`image`	Image metadata.	A receipt photo.
`file`	Generic file metadata.	An attached invoice.

Built-In Values And Functions

code

1time current = time.now()2string generated_id = nanoid()3string short_id = nanoid(12)

Built-in	Result	Rule
`time.now()`	`time`	Returns the current timestamp and accepts no arguments.
`nanoid()`	`string`	Generates a unique identifier with the default length.
`nanoid(length)`	`string`	Generates a unique identifier using a numeric length.

time.now() and nanoid are available in full/backend Nenu and Page Script. Current-user identity is supplied through an explicit platform contract; do not invent a bare uid binding or treat it as a replacement for the platform-owned User type.

Image And File Metadata

code

1type ExpenseReceipt {2  photo: image?3  invoice: file?4}56with receipt.photo as photo {7  photo_url = photo.url8  photo_width = photo.width9}1011with receipt.invoice as invoice {12  invoice_name = invoice.name13  invoice_size = invoice.size14}

Type	Fields
`image`	`url: string`, `name: string`, `size: number`, `width: number`, `height: number`
`file`	`url: string`, `name: string`, `size: number`

The Platform-Provided User Type

User represents a person supplied by the platform. Application entities may reference it, runnable inputs may resolve it, and examples may pass it through typed fields. Application source must not redeclare that platform type.

code

1entity Expense {2  room_id: string @index3  payer: User4  title: string5  amount: number6  note: string?7  receipt: image?8  status: ExpenseStatus9}

Request And Response

An API runnable is an implicit typed function. App Marché metadata supplies its Request input and Response output. Source reads request.field and returns Response { ... }; it must not declare either contract as a source type.

code

1amount = request.amount2return Response { amount }

Managed Entity Fields

App Marché entity records receive managed identity and time fields. Treat id, createdAt, and updatedAt as generated fields; do not redeclare them in an application entity body.

Field	Type	Owner
`id`	`string`	Generated entity identity.
`createdAt`	`time`	Generated creation time.
`updatedAt`	`time`	Generated last-update time.

Common Mistakes

Mistake	Correction
Redeclare a platform type	Consume the type supplied by the active contract.
Guess fields on `User`	Use only the published platform contract.
Declare Request or Response in runnable source	Define those contracts in runnable metadata.
Treat image or file as a URL string	Use the documented media metadata fields.

Continue Learning

Entities Define application-owned records without redeclaring platform types or managed fields.API Runnables Use Request and Response as an enforced workflow contract.