project-iris 0.0.1

package/src/iris_bundle/frameworks/iris-core/images/old_favicon.svg

@@ -0,0 +1,40 @@
+<svg width="32" height="32" viewBox="0 0 32 32" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <!-- Pixel art S from specs.md logo -->
+  <g stroke="#3D2F2F" stroke-width="0.5">
+    <!-- Top row -->
+    <rect x="8" y="2" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="12" y="2" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="16" y="2" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="20" y="2" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="24" y="2" width="4" height="4" fill="#CD6B4D"/>
+
+    <!-- Second row -->
+    <rect x="4" y="6" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="8" y="6" width="4" height="4" fill="#CD6B4D"/>
+
+    <!-- Third row (left side) -->
+    <rect x="4" y="10" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="8" y="10" width="4" height="4" fill="#CD6B4D"/>
+
+    <!-- Middle row -->
+    <rect x="8" y="14" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="12" y="14" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="16" y="14" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="20" y="14" width="4" height="4" fill="#CD6B4D"/>
+
+    <!-- Fifth row (right side) -->
+    <rect x="20" y="18" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="24" y="18" width="4" height="4" fill="#CD6B4D"/>
+
+    <!-- Sixth row (right side) -->
+    <rect x="20" y="22" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="24" y="22" width="4" height="4" fill="#CD6B4D"/>
+
+    <!-- Bottom row -->
+    <rect x="4" y="26" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="8" y="26" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="12" y="26" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="16" y="26" width="4" height="4" fill="#CD6B4D"/>
+    <rect x="20" y="26" width="4" height="4" fill="#CD6B4D"/>
+  </g>
+</svg>

package/src/iris_bundle/frameworks/iris-core/interview.yaml

@@ -0,0 +1,48 @@
+schemaVersion: 1
+questions:
+  - id: goal
+    field: goal
+    required: true
+    text: "What is the product goal?"
+
+  - id: target_users
+    field: targetUsers
+    required: true
+    text: "Who are the target users?"
+
+  - id: problem
+    field: problem
+    required: true
+    text: "What problem are we solving?"
+
+  - id: value_prop
+    field: valueProp
+    required: true
+    text: "What is the value proposition?"
+
+  - id: mvp_scope
+    field: mvpScope
+    required: true
+    text: "What is in/out of MVP scope?"
+
+  - id: success_criteria
+    field: successCriteria
+    required: true
+    text: "What are the success criteria?"
+
+  - id: platforms
+    field: platforms
+    required: true
+    text: "Target platforms? (iOS/Android/Web)"
+
+  - id: integrations
+    field: integrations
+    text: "Required integrations?"
+
+  - id: frontend_stack
+    field: frontendStack
+    text: "Frontend stack?"
+
+  - id: backend_stack
+    field: backendStack
+    text: "Backend stack?"

package/src/iris_bundle/frameworks/iris-core/memory-bank/PRFAQ.md

@@ -0,0 +1,193 @@
+# irismd PRFAQ
+
+## Press Release
+
+### iris.md Launches Open-Source AI-DLC Implementation for AI-Native Engineers
+
+**irismd brings AWS AI-Driven Development Lifecycle to Claude Code, Cursor, and GitHub Copilot**
+
+Today, iris.md announces the release of irismd, an open-source implementation of AWS's AI-Driven Development Lifecycle (AI-DLC) methodology. This tool enables AI-native engineers to leverage a multi-agent orchestration system that transforms how software is built - from intent capture through deployment.
+
+"Traditional development methods were built for human-driven, long-running processes," said the iris.md team. "AI-DLC reimagines the development lifecycle with AI as a central collaborator, enabling rapid cycles measured in hours or days rather than weeks."
+
+irismd provides four specialized AI agents - Master, Inception, Construction, and Operations - that guide developers through the complete software lifecycle. Each agent is equipped with domain-specific skills and follows the AI-DLC principle that "AI drives workflows by breaking down high-level intents into actionable tasks, while humans serve as approvers, validating and confirming decisions at critical junctures."
+
+Key features include:
+
+- **Multi-Tool Support**: Works with Claude Code, Cursor, and GitHub Copilot
+- **Memory Bank System**: File-based artifact storage for project context
+- **Bolt Execution**: Rapid iteration cycles with DDD, TDD, BDD, and Spike bolt types
+- **Standards-Driven**: Built-in facilitation for tech-stack, coding standards, and architecture decisions
+- **Human Oversight**: Validation points at every stage to catch errors early
+
+irismd is available now at <https://iris.md> and can be installed via npm.
+
+---
+
+## FAQ
+
+### General
+
+**Q: What is irismd?**
+A: irismd is an open-source implementation of AWS's AI-Driven Development Lifecycle (AI-DLC) methodology. It provides a multi-agent system that orchestrates the software development process from intent capture through deployment.
+
+**Q: What is AI-DLC?**
+A: AI-DLC is a reimagined, AI-native software development methodology created by AWS. It differs from traditional methods by having AI drive workflows and break down high-level intents into actionable tasks, while humans validate and approve decisions. It features three phases: Inception, Construction, and Operations.
+
+**Q: Who is irismd for?**
+A: irismd is designed for AI-native engineers who want to leverage AI throughout the development lifecycle, not just for code generation. It's suited for building complex systems that demand architectural complexity, trade-off management, and scalability.
+
+**Q: What agentic coding tools are supported?**
+A: Currently supported:
+
+- Claude Code (Anthropic)
+- Cursor
+- GitHub Copilot
+
+### Installation & Setup
+
+**Q: How do I install irismd?**
+A: Install via npx:
+
+```bash
+npx irismd install
+```
+
+The installer will detect available agentic coding tools and guide you through setup.
+
+**Q: What gets installed?**
+A: irismd installs:
+
+- Agent definitions (markdown files)
+- Skills for each agent
+- Templates for artifacts
+- Slash commands
+- Memory bank structure
+
+**Q: Can I use multiple agentic coding tools?**
+A: Yes. During installation, you can select multiple tools and irismd will install to all of them.
+
+### Agents & Skills
+
+**Q: What agents are available?**
+A: Four agents:
+
+1. **Master Agent** - Central orchestrator that analyzes project state and routes to specialist agents
+2. **Inception Agent** - Handles requirements, decomposition into units, and story creation
+3. **Construction Agent** - Executes bolts through domain design, logical design, code, and test stages
+4. **Operations Agent** - Manages deployment, verification, and monitoring
+
+**Q: How do I invoke an agent?**
+A: Use slash commands in your agentic coding tool:
+
+- `/irismd-master-agent` - Master agent
+- `/irismd-inception-agent` - Inception agent
+- `/irismd-construction-agent` - Construction agent
+- `/irismd-operations-agent` - Operations agent
+
+**Q: What are skills?**
+A: Skills are focused capabilities within each agent. For example, the Inception Agent has skills for creating intents, gathering requirements, defining system context, decomposing into units, and creating stories.
+
+### AI-DLC Concepts
+
+**Q: What is an Intent?**
+A: An Intent is a high-level statement of purpose that encapsulates what needs to be achieved - whether a business goal, feature, or technical outcome. It serves as the starting point for AI-driven decomposition.
+
+**Q: What is a Unit?**
+A: A Unit is a cohesive, self-contained work element derived from an Intent. Units are loosely coupled and can be developed and deployed independently. They're analogous to Subdomains in DDD or Epics in Scrum.
+
+**Q: What is a Bolt?**
+A: A Bolt is the smallest iteration in AI-DLC, designed for rapid implementation. Unlike Sprints (weeks), Bolts are measured in hours or days. They emphasize intense focus and high-velocity delivery.
+
+**Q: What are the AI-DLC phases?**
+A: Three phases:
+
+1. **Inception** - Capture intents, elaborate into stories/NFRs, decompose into units, plan bolts
+2. **Construction** - Execute bolts through domain design → logical design → code → test
+3. **Operations** - Deploy, verify, and monitor
+
+### Bolt Types
+
+**Q: What bolt types are available?**
+A: Two bolt types:
+
+1. **DDD Construction Bolt** - Domain-Driven Design stages (model, design, ADR, implement, test)
+2. **Simple Construction Bolt** - Lightweight stages for UI, integrations, utilities (plan, implement, test)
+
+**Q: How do I choose a bolt type?**
+A: The Construction Agent recommends bolt types based on the unit's requirements. DDD is default for complex business logic, Simple for UI, integrations, and utilities.
+
+### Memory Bank
+
+**Q: What is the Memory Bank?**
+A: The Memory Bank is a file-based storage system for all project artifacts. It maintains context across agent sessions and provides traceability between artifacts.
+
+**Q: What's stored in the Memory Bank?**
+A:
+
+- `intents/` - Feature intents and their decomposition
+- `bolts/` - Bolt execution instances
+- `standards/` - Project standards (tech-stack, coding, architecture)
+- `operations/` - Deployment and monitoring context
+
+### Standards
+
+**Q: What standards does irismd support?**
+A: Five standards types:
+
+1. **Tech Stack** - Languages, frameworks, databases, infrastructure
+2. **Coding Standards** - Formatting, linting, naming, testing strategy
+3. **System Architecture** - Architecture style, API design, state management
+4. **UX Guide** - Design system, styling, accessibility
+5. **API Conventions** - API style, versioning, response formats
+
+**Q: How are standards created?**
+A: The Master Agent's `project-init` skill facilitates guided conversations to establish standards. It uses facilitation guides to help users make informed decisions.
+
+### Human Oversight
+
+**Q: Why is human oversight important in AI-DLC?**
+A: Human oversight functions as a "loss function" - catching and correcting errors early before they snowball downstream. Each validation step transforms artifacts into semantically rich context for the next stage.
+
+**Q: Where are the validation points?**
+A: Key validation points:
+
+- After requirements elaboration
+- After unit decomposition
+- After story creation
+- After each bolt stage (domain design, logical design, code, test)
+- Before deployment
+
+### Comparison
+
+**Q: How is AI-DLC different from Agile/Scrum?**
+A: Key differences:
+
+| Aspect | Agile/Scrum | AI-DLC |
+|--------|-------------|--------|
+| Iteration duration | Weeks (Sprints) | Hours/days (Bolts) |
+| Driver | Human-driven | AI-driven, human-validated |
+| Design techniques | Out of scope | Integrated (DDD, TDD, BDD) |
+| Phases | Iterative sprints | Iterative with 3 phases (Inception, Construction, Operations) |
+| Rituals | Daily standups, retrospectives | Mob Elaboration, Mob Construction |
+
+**Q: Can I use irismd with existing Agile workflows?**
+A: AI-DLC is designed as a reimagination, not a retrofit. However, familiar concepts (user stories, acceptance criteria) are retained to ease transition.
+
+### Troubleshooting
+
+**Q: Agents don't seem to remember previous context?**
+A: Each agent invocation starts fresh. Agents read context from the Memory Bank at startup. Ensure artifacts are saved after each step.
+
+**Q: How do I reset project state?**
+A: Clear the `memory-bank/` directory to reset all artifacts. To remove irismd entirely:
+
+1. Delete the `.irismd/` directory
+2. Delete tool-specific command files (`.claude/commands/irismd-*.md`, `.cursor/commands/irismd-*.md`, `.github/copilot/commands/irismd-*.md`)
+3. Optionally delete `memory-bank/` if you don't need to preserve project context
+
+**Q: Where can I get help?**
+A:
+
+- Documentation: <https://iris.md>
+- Issues: <https://github.com/fabriqaai/irismd/issues>

package/src/iris_bundle/frameworks/iris-core/memory-bank/bolts/016-analytics-tracker/bolt.md

@@ -0,0 +1,122 @@
+---
+id: 016-analytics-tracker
+unit: 001-analytics-tracker
+intent: 007-installer-analytics
+type: simple-construction-bolt
+status: complete
+stories:
+  - 001-initialize-mixpanel
+  - 002-generate-machine-hash
+  - 003-generate-session-id
+  - 004-detect-shell
+  - 005-detect-telemetry-disabled
+  - 006-track-installer-started
+  - 007-track-ides-confirmed
+  - 008-track-flow-selected
+  - 009-track-installation-completed
+  - 010-track-installation-failed
+  - 011-fire-and-forget
+  - 012-geolocation-support
+created: 2025-12-28T12:00:00Z
+started: 2025-12-28T18:30:00Z
+completed: "2025-12-28T17:29:23Z"
+current_stage: null
+stages_completed:
+  - name: plan
+    completed: 2025-12-28T18:35:00Z
+    artifact: implementation-plan.md
+  - name: implement
+    completed: 2025-12-28T18:50:00Z
+    artifact: implementation-walkthrough.md
+  - name: test
+    completed: 2025-12-28T19:00:00Z
+    artifact: test-walkthrough.md
+requires_bolts: []
+enables_bolts:
+  - 017-privacy-documentation
+requires_units: []
+blocks: false
+complexity:
+  avg_complexity: 2
+  avg_uncertainty: 1
+  max_dependencies: 1
+  testing_scope: 2
+---
+
+# Bolt: 016-analytics-tracker
+
+## Overview
+
+Implement Mixpanel analytics integration for the irismd installer. This bolt adds anonymous usage tracking to understand adoption patterns, IDE preferences, and installation behavior.
+
+## Objective
+
+Create an AnalyticsTracker module that:
+- Generates stable machine ID (salted SHA-256 of hostname)
+- Generates unique session ID per run
+- Detects shell environment
+- Sends events to Mixpanel (fire-and-forget)
+- Respects opt-out environment variables
+
+## Stories Included
+
+1. **Initialize Mixpanel** with project token
+2. **Generate machine hash** (salted SHA-256 of hostname) as distinct_id
+3. **Generate session ID** (random UUID) per run
+4. **Detect shell** (zsh, bash, powershell, cmd, fish)
+5. **Detect telemetry disabled** via environment variables
+6. **Track installer_started** event
+7. **Track ides_confirmed** event with count and list
+8. **Track flow_selected** event
+9. **Track installation_completed** event per IDE
+10. **Track installation_failed** event with error category
+11. **Fire-and-forget** pattern (non-blocking)
+12. **Geolocation support** (Mixpanel handles from IP)
+
+## Bolt Type
+
+**Type**: Simple Construction Bolt
+**Definition**: `.irismd/aidlc/templates/construction/bolt-types/simple-construction-bolt.md`
+
+## Stages
+
+- [ ] **1. Spec**: Create implementation plan
+- [ ] **2. Implement**: Build analytics module
+- [ ] **3. Test**: Verify tracking works
+
+## Dependencies
+
+### Requires
+- None (standalone module)
+
+### Enables
+- 017-privacy-documentation
+
+## Files to Create/Modify
+
+```
+src/
+├── analytics/
+│   ├── index.ts           # Exports analytics singleton
+│   ├── tracker.ts         # AnalyticsTracker class
+│   ├── machine-id.ts      # getMachineId() - salted SHA-256
+│   └── env-detector.ts    # Shell and CI detection
+```
+
+## Success Criteria
+
+- [ ] Mixpanel SDK initialized correctly
+- [ ] Machine ID is consistent across runs on same machine
+- [ ] Session ID is unique per run
+- [ ] Shell detected correctly on macOS, Linux, Windows
+- [ ] Telemetry disabled when env vars set
+- [ ] All 5 events tracked with correct properties
+- [ ] Events are fire-and-forget (non-blocking)
+- [ ] Failures are silent (never break installation)
+- [ ] No PII collected (GDPR compliant)
+
+## Notes
+
+- Mixpanel token will be embedded in source (acceptable for analytics)
+- Salt prevents reverse-lookup of hostname hash
+- Must add `mixpanel` as a dependency to package.json

package/src/iris_bundle/frameworks/iris-core/memory-bank/bolts/016-analytics-tracker/implementation-plan.md

@@ -0,0 +1,172 @@
+---
+stage: plan
+bolt: 016-analytics-tracker
+created: 2025-12-28T18:30:00Z
+---
+
+# Implementation Plan: Analytics Tracker
+
+## Objective
+
+Build a Mixpanel analytics module for the irismd installer that tracks anonymous usage patterns while respecting user privacy and opt-out preferences. The module must be fire-and-forget (non-blocking) and fail silently to never disrupt installations.
+
+## Deliverables
+
+### Files to Create
+
+```
+src/analytics/
+├── index.js           # Singleton export: analytics instance
+├── tracker.js         # AnalyticsTracker class with all tracking methods
+├── machine-id.js      # getMachineId() - salted SHA-256 of hostname
+└── env-detector.js    # detectShell(), isTelemetryDisabled()
+```
+
+### Functions to Implement
+
+| Function | File | Purpose |
+|----------|------|---------|
+| `getMachineId()` | machine-id.js | Salted SHA-256 hash of hostname as distinct_id |
+| `getSessionId()` | tracker.js | Random UUID per run |
+| `detectShell()` | env-detector.js | Return shell name (zsh, bash, powershell, cmd, etc.) |
+| `isTelemetryDisabled()` | env-detector.js | Check env vars and CLI flag |
+| `init()` | tracker.js | Initialize Mixpanel with IDs |
+| `trackInstallerStarted()` | tracker.js | installer_started event |
+| `trackIdesConfirmed()` | tracker.js | ides_confirmed event with ide_count, ides[] |
+| `trackFlowSelected()` | tracker.js | flow_selected event |
+| `trackInstallationCompleted()` | tracker.js | installation_completed with ide, flow, duration_ms, files_created |
+| `trackInstallationFailed()` | tracker.js | installation_failed with ide, error_category, flow |
+
+## Dependencies
+
+### External Dependencies
+
+| Package | Purpose | Notes |
+|---------|---------|-------|
+| `mixpanel` | Mixpanel Node.js SDK | Must add to package.json |
+
+### Internal Dependencies
+
+| Module | Purpose |
+|--------|---------|
+| Node.js `crypto` | SHA-256 hashing and UUID generation |
+| Node.js `os` | hostname() for machine ID |
+
+## Technical Approach
+
+### Machine ID Generation
+
+```javascript
+const salt = 'irismd-analytics-v1';
+const machineId = crypto.createHash('sha256')
+    .update(salt + os.hostname())
+    .digest('hex');
+```
+
+- Salt is constant to prevent rainbow table attacks
+- Same machine always produces same hash
+- No way to reverse-lookup the hostname
+
+### Session ID Generation
+
+```javascript
+const sessionId = crypto.randomUUID();
+```
+
+- Unique per installer run
+- Used to group events within a single session
+
+### Base Properties (All Events)
+
+```javascript
+{
+    distinct_id: machineId,
+    session_id: sessionId,
+    $os: process.platform,
+    shell: detectShell(),
+    node_version: process.version,
+    irismd_version: pkg.version
+}
+```
+
+### Telemetry Disabled Check
+
+Check in this priority order:
+1. `--no-telemetry` CLI flag (process.argv)
+2. `SPECSMD_TELEMETRY_DISABLED=1`
+3. `DO_NOT_TRACK=1`
+4. CI environment detection:
+   - `CI=true`
+   - `GITHUB_ACTIONS=true`
+   - `GITLAB_CI=true`
+   - `JENKINS_URL` is set
+   - `CIRCLECI=true`
+
+### Fire-and-Forget Pattern
+
+```javascript
+track(eventName, properties = {}) {
+    if (!this.enabled) return;
+
+    try {
+        this.mixpanel.track(eventName, {
+            ...this.baseProperties,
+            ...properties
+        });
+        // No await - fire and forget
+    } catch (e) {
+        // Silent failure - never break installation
+    }
+}
+```
+
+### Shell Detection
+
+| Platform | Check | Example Values |
+|----------|-------|----------------|
+| Unix | `process.env.SHELL` basename | zsh, bash, fish, sh |
+| Windows | `process.env.ComSpec` | powershell, pwsh, cmd |
+| Unknown | fallback | "unknown" |
+
+## Acceptance Criteria
+
+### Core Functionality
+- [ ] Mixpanel SDK initialized with project token
+- [ ] Machine ID is consistent across runs on same machine
+- [ ] Session ID is unique per run
+- [ ] All 5 event types tracked with correct properties
+- [ ] Events include all base properties
+
+### Privacy & Opt-out
+- [ ] Telemetry disabled when SPECSMD_TELEMETRY_DISABLED=1
+- [ ] Telemetry disabled when DO_NOT_TRACK=1
+- [ ] Telemetry disabled in CI environments
+- [ ] --no-telemetry CLI flag works
+
+### Reliability
+- [ ] Analytics adds <50ms to installation time
+- [ ] Silent failure on network errors
+- [ ] Never breaks installation on analytics failure
+- [ ] Works offline without errors
+
+### Quality
+- [ ] No PII collected (GDPR compliant)
+- [ ] Code follows project coding standards
+- [ ] Linting passes
+
+## Events Reference
+
+| Event | Properties | When Fired |
+|-------|------------|------------|
+| `installer_started` | base only | Installer begins |
+| `ides_confirmed` | ide_count, ides[] | After IDE selection confirmed |
+| `flow_selected` | flow | After flow selection |
+| `installation_completed` | ide, flow, duration_ms, files_created | Per IDE after successful install |
+| `installation_failed` | ide, error_category, flow? | Per IDE after failed install |
+
+## Notes
+
+- Mixpanel project token will be embedded in source (standard practice for analytics)
+- Geolocation is handled by Mixpanel from IP address - no action needed
+- Package.json must be updated to include mixpanel dependency
+- Integration with installer CLI will be done by calling tracking methods at appropriate points

package/src/iris_bundle/frameworks/iris-core/memory-bank/bolts/016-analytics-tracker/implementation-walkthrough.md

@@ -0,0 +1,56 @@
+---
+stage: implement
+bolt: 016-analytics-tracker
+created: 2025-12-28T18:45:00Z
+---
+
+# Implementation Walkthrough: Analytics Tracker
+
+## Summary
+
+Implemented a Mixpanel-based analytics module for the irismd installer. The module tracks anonymous usage patterns using stable machine IDs and unique session IDs, while respecting user privacy through multiple opt-out mechanisms.
+
+## Structure Overview
+
+The analytics module follows a modular architecture with separation of concerns:
+- Machine ID generation is isolated for testability
+- Environment detection handles platform differences
+- The tracker class provides a singleton interface with fire-and-forget semantics
+
+## Completed Work
+
+- [x] `src/lib/analytics/index.js` - Singleton export providing the main analytics interface
+- [x] `src/lib/analytics/tracker.js` - AnalyticsTracker class with all tracking methods and Mixpanel integration
+- [x] `src/lib/analytics/machine-id.js` - Stable machine identifier using salted SHA-256 of hostname
+- [x] `src/lib/analytics/env-detector.js` - Shell detection and telemetry opt-out checks
+- [x] `src/package.json` - Added mixpanel dependency (^0.18.0)
+
+## Key Decisions
+
+- **Singleton Pattern**: Used a class instance export rather than static methods to maintain state (machineId, sessionId, enabled flag) across the application lifecycle
+
+- **Lazy Mixpanel Loading**: The Mixpanel SDK is required inside init() rather than at module load, preventing blocking if analytics is disabled
+
+- **Fire-and-Forget**: All track() calls are synchronous no-ops that queue events internally. No await/promise handling ensures zero latency impact
+
+- **Silent Failures**: All Mixpanel operations are wrapped in try/catch with empty catch blocks - analytics should never break installation
+
+- **Salt in Code**: The salt is a constant in source code rather than environment variable - this is intentional to ensure consistent machine IDs across all installations
+
+## Deviations from Plan
+
+None - implementation follows the plan exactly.
+
+## Dependencies Added
+
+- [x] `mixpanel` (^0.18.0) - Mixpanel Node.js SDK for event tracking
+
+## Developer Notes
+
+- The Mixpanel token is embedded in source code - this is standard practice for analytics (client-side analytics tokens are public by design)
+
+- Machine ID uses a constant salt (`irismd-analytics-v1`) - changing this would break ID consistency for all users
+
+- The tracker is a singleton - calling init() multiple times is safe (returns cached enabled state)
+
+- Integration with installer.js is not included in this bolt - the tracking methods are ready to be called at appropriate points