Modules - Point docs

Summary

Point programs are grouped with module names and connected through use imports. The CLI resolves a dependency graph before check-all and project builds.

Syntax

module Billing

record Invoice
  total: Int

use http

module Name sets the module name for semantic refs
use http imports a built-in capability (same as use std.http) — see Capabilities
use std.<module> explicit std import
use Module from "./path.point" links another file (see examples/multi-file/order.point)

Semantics

The CLI discovers examples/**/*.point, std/**/*.point, and compiler/**/*.point for project commands (check-all, build-all, build-ts-all, etc.). Dependencies are checked in topological order. Cycles are rejected.

Public symbols from dependencies are visible to importers after point check.

Compiler note

use links form a directed graph checked in topological order. Cycles are rejected.

Example

From the repository std-usage example:

module StdUsage

calculation pass through
  input value: Text
  output result: Text
  result is value

use text
use json

Multi-file layout also lives under examples/multi-file/ in the repository.

Common mistakes

Broken relative paths (Cannot resolve Point module)
Cyclic imports between files

Agent diagnostic notes

Run project-wide point check-all when changing shared modules
Semantic refs include the module segment: point://semantic/Billing/...