Read-only introspection over the callable PTC-Lisp surface.

Backs the dir, apropos, doc, export-meta, and source builtins. dir, export-meta, and source describe the attached prelude. apropos and doc additionally expose fixed built-ins and the bounded Java surface from PtcRunner.Lisp.Registry. The same answers are produced in the REPL, in workflow and mission source, and inside a prelude export reading another prelude's documentation — there is no REPL-only path.

Ref arguments accept a string or a {:symbol_ref, name} runtime value (from a quoted symbol, or from the analyzer's bare-symbol rewrite on these forms). meta is intentionally not included: in Clojure it is an ordinary function over values, not a discovery form. source resolves only against the attached prelude's compile-time source_index — there is no registry fallthrough.

Attached prelude visibility

Only public export records (%PtcRunner.Lisp.Prelude.Export{}), which cover both :prompt and :discoverable visibility. Private defn- helpers have no export record and are unreachable by qualified call, so they are absent from dir/apropos/doc/export-meta. source is the exception: it can reveal a private helper that is transitively reachable from a visible public export, via Prelude.source_index (not form_graph callables).

Namespaces are derived from the visible export set rather than from Prelude.namespaces/1, so a namespace holding only private helpers does not appear in namespaces/2.

Visibility filter

Callers pass a predicate over export records rather than any runtime context, keeping this module pure. PtcRunner.Lisp.Eval.Apply builds it from the evaluation context so that what a program can discover matches what it can call: PtcRunner.Lisp.Eval.Context.prelude_ref_visible?/2 supplies the strict_transitive_calls half, and the run's prelude_export_mask supplies the discovery half. A narrowed session grant needs no filter here — it hands the run a prelude whose exports list is already the narrow set.

How the reported effect is bounded

Export.effect joins an export's own declaration with those of the prelude helpers it calls, but not with the effects of the capabilities it reaches. The authoritative value is the mission-resolved effect PtcRunner.Kernel.MissionInventory publishes, which adds that last join: a wrapper declaring :read over a capability installed as :write resolves to :write. Producing it needs the mission's capability set, which this layer does not have.

Reporting the raw declaration would therefore let a program read :read for an operation the inventory calls :write — the direction that invites repeating an irreversible call. Omitting the effect is no better: the inventory covers only Prelude.prompt_exports/1, so a :discoverable export is callable with no effect stated anywhere.

So the reported effect is deliberately weakened rather than dropped. An export that reaches no capability is reported as declared. An export that does reach one is reported as :write if anything in its chain declares :write, and :unknown otherwise. It can still fall short of a :write the inventory resolves, but it never calls something :read that touches a capability, so no answer here presents an unresolved effect as safe.

Misses

An exact attached export occupies its ref before its visibility filter is applied. A hidden attached ref therefore cannot fall through to registry documentation for the same spelling. Otherwise doc falls back to the registry, and apropos merges visible attached refs with canonical registry names. An unknown or malformed ref is a miss, not a failure.