No side effects, no surprises.

  1. Welcome
    1. What is the V language?
    2. What problem does this solve?
    3. “Working knowledge” is a critical dependency
    4. System documentation through executable rulebooks
    5. Usage scenarios
  2. Traits
    1. No side effects
    2. Declarative statements
    3. Objects
    4. Syntactic rules
    5. Sample
  3. Interpreter
    1. Language vs. Interpreter
    2. Rulebooks
    3. VLI Architecture
    4. Processing flow
    5. Object scope
    6. Object composer
    7. Dependency tree
    8. Resource evaluator
    9. Variable substitution
    10. Rule validator
    11. Trip-point emitter
  4. Installation
    1. Prerequisites
    2. Download
    3. Setup
Internet standards Memo must word Changed simple How A Simple 500-Word Memo Changed the Way We Talk About the Internet In March of 1997, Scott Bradner penned a short memo titled 'Key Words For Use in RFCs to Indicate Requirement Levels'. It is more commonly referred to as simply RFC 2119.

The V Language

The V language is a domain-specific language for capturing the operational values of a host computer's resources and for checking their validity against user-defined rules.

V is nullipotent, declarative, and interpreted. V operates on objects which describe host resource variables and user-defined rules. Objects are dynamically typed and may belong to namespaces. V is extensible by design: its interpreter can discover and use third-party plugin modules.

V is well suited to helping system administrators with monitoring computer systems safely and without side effects.