Artifact interface

In Simon’s account, an artifact is an interface between an inner environment—its substance and organization—and an outer environment in which it operates. Whether it serves a purpose depends on the relation between its construction, that purpose, and its surroundings. “Interface” here names an analytical boundary, not just a screen or an API. (Chapter 1, printed pp. 5–9)¹

Uses and boundaries

Simon uses clocks to show why the environment matters: a mechanism adequate on land may fail aboard a moving ship. Similar functions can be realized by different internal mechanisms. Functional similarity therefore does not establish identical construction, and a functional description alone does not explain how adaptation arose. (Chapter 1, printed pp. 6–8)¹

The relation to Agent is a complementary viewpoint: perception–action analysis describes interaction, whereas the artifact perspective asks how internal organization fits an environment and purpose. The boundary must be specified for the particular analysis; an entire software platform is not automatically the agent’s inner environment.

Operational example

An illustrative application is a scheduling assistant: its planner and stored commitments form an inner organization; calendar services, users, and appointment constraints form the chosen outer environment. Evaluate whether it schedules correctly under delayed calendar updates, rather than evaluating its planner only with perfect inputs. This is an Atlas application, not Simon’s own example.

Footnotes

1. Simon, Herbert A. The Sciences of the Artificial. Third edition. MIT Press, 1996. ISBN 9780262193740 (hardcover). Publisher page, paperback ISBN 9780262691918. Inspected Chapter 1, printed pp. 5–9 (PDF pp. 17–21 in the privately held copy). ↩ ↩²