Developer Agreement Policy

1. DEFINITIONS

For the purposes of this Developer Agreement Policy, the following terms shall carry the explicit meanings defined below. Failure to understand these definitions does not excuse a violation of the policies governing them.

• Stellr, LLC: Refers to the corporate entity providing the underlying AI infrastructure, centralized execution environment, and associated developer ecosystem.
• Developer: Any individual, corporation, or entity that utilizes Stellr’s SDKs, APIs, or infrastructure to create, modify, or distribute digital products within the Stellr ecosystem.
• OrrinApps: The overarching umbrella platform and execution environment managed by Stellr, LLC, which hosts, routes, and manages the lifecycle of deployed AI modules.
• Orrin Marketplace: The public-facing distribution and publishing layer where end-users can discover, evaluate, and authorize Applications, Tools, and Agents created by Developers.
• Tool: A discrete AI function or capability. Tools are not restricted to a single action and may encompass multiple interconnected actions; however, the overarching Tool must be distinctly purposed to a specific ordeal, domain, or operational goal.
• Application: A comprehensive product or software suite built leveraging Stellr infrastructure, potentially combining multiple Tools and sophisticated logic to serve a broader user need.
• Agent: An autonomous or semi-autonomous system capable of persistent state, context-gathering, and multi-step execution without continuous explicit human prompting.
• SDK (Software Development Kit): The proprietary libraries, documentation, code samples, and protocols provided by Stellr to facilitate integration with our execution engine.
• API (Application Programming Interface): The endpoints and communication protocols provided by Stellr allowing Developer systems to interact programmatically with Stellr infrastructure.
• OAuth Consent Screen: The mandatory user interface provided by Stellr through which end-users explicitly review, grant, or deny permissions. Stellr handles the underlying logic and overall flow of these screens, while Developers manage the structural routing and UI triggers for invocation.
• User Data: Any information, context, behavioral vectors, text, media, or metadata generated by, pertaining to, or owned by the end-user that is processed through the Stellr ecosystem.
• Marketplace: Shorthand reference to the Orrin Marketplace as defined above.

2. PLATFORM OVERVIEW

The Stellr ecosystem is fundamentally designed to accelerate the development of context-aware, promptless AI technologies. Our platform bridges the gap between raw programmatic action and nuanced human intent.

As a Developer, you are granted access to a sophisticated AI infrastructure that translates user context into actionable data. The Orrin Marketplace serves as the exclusive publishing model for distributing your creations to end-users. It is a highly curated environment designed to foster trust and reliability.

To maintain this trust, Stellr operates a rigorous review and approval system. All Tools, Applications, and Agents must be vetted before public distribution. We provide the runtime execution environment - ensuring low latency and contextual awareness - but we also act as the ultimate gatekeeper. Stellr’s role as infrastructure provider grants us the absolute authority to monitor, manage, and restrict the flow of executions to protect user safety and platform integrity.

3. DEVELOPER RIGHTS AND RESPONSIBILITIES

By building on the Stellr platform, Developers are granted specific operational privileges, balanced by strict ecosystem responsibilities.

• Intellectual Property Ownership: Developers unconditionally retain full ownership of their proprietary code, business logic, and custom application designs. Stellr claims no ownership over the unique intellectual property you bring to the ecosystem.
• Branding Compliance: Developers must strictly comply with all Stellr and Orrin branding guidelines.
• Honesty in Representation: Developers must not misrepresent the ownership, origin, or capabilities of their technology. You may not claim proprietary ownership over Stellr’s underlying context engines or foundational models.
• Conditional Attribution: Stellr does not require entities to publicly announce usage of our tools or services under normal operations. However, mandatory public attribution is required if Stellr tools or services have enabled profound advancements within a technology, product, or industry.
• Metadata Accuracy: Developers must maintain absolute honesty and transparency in the naming, descriptions, marketing copy, and metadata of their submissions. "Bait-and-switch" descriptions are grounds for immediate permanent bans.

4. TOOL AND APPLICATION BEHAVIOR RULES

Because the Stellr ecosystem powers autonomous and semi-autonomous Agents, the predictability and design of your Tools and Applications are paramount. Poor design or unpredictable behavior poses a severe security risk.

• Design & UX Expectations: Applications must feature purposeful, cohesive user experiences. Even though tools can contain multiple actions, those actions must clearly support a specific operational ordeal. Developers are expected to structure their application flows intuitively, ensuring users are never surprised by systemic behaviors.
• Declared Functionality: Tools must possess a consistent, explicitly declared functionality. The behavior exhibited during the review process must be the exact behavior exhibited in production.
• No Hidden Behavior: Applications and Tools must not contain hidden payloads, undeclared background tracking, or secondary execution paths that bypass the platform's standard transparency measures.
• No Dynamic Bait-and-Switch: Dynamic behavior changes that alter the core purpose of a Tool post-approval - specifically those designed to mislead users or bypass review constraints - are strictly prohibited.
• Prohibition on Impersonation: Tools must never impersonate Stellr systems, Orrin core infrastructure, or system-level prompts. Interfaces must clearly distinguish Developer-created actions from platform-native actions.
• Stability of Purpose: Tools must maintain a stable core purpose throughout their lifecycle. Significant pivots in functionality require a new submission and a fresh user consent cycle.

5. DATA PRIVACY AND HANDLING

Data within a context-aware AI ecosystem is highly sensitive. Stellr enforces a policy of aggressive data minimization and absolute respect for user privacy.

• Strict Data Minimization: Developers MAY NOT harvest, store, cache, or retain User Data beyond what is strictly and immediately necessary for the functional execution of the Tool or Application.
• Prohibition on Repurposing: Under no circumstances may User Data obtained via the Stellr ecosystem be repurposed for unauthorized analytics, shadow profiling, cross-site tracking, advertising, or resale to third-party data brokers.
• External API Liability: If a Developer's Tool transmits User Data to an external, third-party API or service, the Developer bears absolute and sole responsibility for ensuring that transmission complies with all applicable privacy laws and this Agreement.
• Third-Party Storage: External systems connected to Developer Tools must not improperly store, aggregate, or reuse transmitted contextual data beyond the scope explicitly authorized by the user.
• Scope Compliance: Strict compliance with approved OAuth scopes is mandatory. Attempting to access data outside the granted scopes, or tricking the system to infer out-of-scope data, is a severe violation.
• Explicit Authorization for Sensitive Operations: All operations deemed sensitive (e.g., financial transactions, permanent data deletion, broad communications) require continuous, explicit user authorization, bypassing silent autonomous execution.

6. OAUTH AND CONSENT REQUIREMENTS

User trust is maintained through cryptographic, irrefutable consent. The Stellr OAuth infrastructure is the sole mechanism for authorization.

• Platform Managed Flow: Stellr centrally handles all of the logic and the overall flow of the OAuth Consent Screens. Developers are not permitted to recreate or proxy this logic.
• Developer Implementation Expectations: While Stellr handles the logic, Developers have the flexibility to design the user journey leading up to consent. Developers may choose to build UI allowing users to manually invoke the consent screen, or they must structure their code to ensure that consent screen enforcements are triggered and handled appropriately when a user accesses a gated feature.
• Universal Consent Requirement: All actions, data reads, or state changes affecting user accounts require processing through official Stellr OAuth Consent Screens.
• Clarity of Scopes: Consent requests generated by your application must use plain, non-technical language to clearly describe exactly what permissions are being requested and how the Tool will behave.
• Non-Negotiable Framework: Utilization of the Stellr OAuth authorization framework is mandatory. Developers may not implement alternative, parallel, or obfuscated login/consent mechanisms to bypass platform visibility.

7. MARKETPLACE (ORRIN MARKETPLACE)

The Orrin Marketplace is a curated ecosystem. Access to distribute software to Stellr users is a conditionally granted privilege, heavily monitored for quality assurance.

• Mandatory Review: All submissions, including initial launches and subsequent major updates, are subject to comprehensive technical and policy review by Stellr.
• Sole Discretion: Stellr reserves the right to approve, delay, or deny any submission at its sole and absolute discretion, without obligation to provide exhaustive justification.
• Revocation Rights: Stellr may immediately suspend or revoke any approved Tool or Application at any time if we determine that it:
  • Violates this Developer Agreement or standard operating policies.
  • Causes tangible or intangible harm to end-users.
  • Degrades, harms, or overburdens Stellr infrastructure.
  • Harms the public reputation or integrity of the Stellr ecosystem.
  • Introduces unacceptable security vulnerabilities or privacy risks.
• Review Process Integrity: Stellr will attempt to enforce a fair, uniform, and non-discriminatory review process for all Developers, regardless of size or origin.
• Communication: Developers may be contacted regarding rejected submissions and will generally be provided with required remediation steps, unless the violation was malicious in nature.

8. BRANDING AND ATTRIBUTION

Transparency regarding partnerships and the underlying technology powering applications is essential to maintaining clarity in the ecosystem.

• No Implied Independence: A developer, organization, or external entity cannot present or market their product or service as entirely independent if tools, APIs, or services provided by Stellr are utilized in their application.
• Attribution Exceptions: Stellr does not require entities to publicly announce or broadcast their usage of our tools or services. However, if our tools and services enable profound advancements with a specific technology, product, or industry, explicit public attribution to Stellr is required.
• Prohibition of Implied Partnerships: Entities cannot act as though they are in an official partnership, joint venture, or endorsement relationship with Stellr unless a formalized partnership agreement has been established between Stellr and the end entity.
• No Implied Sole Creation: Developers must not imply that they are the sole creators of the artificial intelligence logic when Stellr's centralized execution and context engines materially contribute to the output.
• Guideline Compliance: All references to Stellr, Orrin, and related product suites must adhere strictly to the rules outlined in our Brand Guidelines.

9. CONTENT AND SAFETY

Stellr maintains a zero-tolerance policy for applications that leverage our context engines to cause harm or spread toxicity.

• Applications, Tools, and Agents must not generate, contain, or facilitate:
  • Harmful Content: Content that promotes self-harm, violence, illegal acts, or terrorism.
  • Discriminatory Content: Hate speech or logic designed to discriminate based on race, gender, religion, sexual orientation, or protected classes.
  • Misleading Functionality: Deepfakes intended to defraud, coordinated disinformation campaigns, or impersonation of public figures.
  • Malicious Behavior: Phishing, malware distribution, unauthorized network scanning, or denial-of-service capabilities.
• Immediate Action: Stellr reserves the right to remove, restrict, or destroy any violating application immediately upon detection, bypassing standard communication protocols if an imminent threat is perceived.

10. TERMINATION AND ENFORCEMENT

We enforce these policies rigorously to protect our users and the developers who operate in good faith.

• Access Suspension: Stellr may suspend or permanently terminate a Developer's access to the Orrin platform, SDKs, and APIs at any time, with or without prior notice.
• Consequences of Violation: Confirmed policy violations will result in the immediate removal of all associated Developer products from the Marketplace and the termination of active OAuth tokens.
• Security Revocations: Stellr may proactively revoke API keys and SDK access if anomalous traffic patterns suggest a security compromise, even without proof of malicious Developer intent.
• Final Authority: All enforcement decisions, technical interpretations of policy, and judgments regarding ecosystem harm are at the sole, unappealable discretion of Stellr, LLC.

11. LIABILITY

The boundary of responsibility between platform infrastructure and Developer implementation is distinct and legally enforced.

• Sole Developer Responsibility: Developers are solely, entirely, and exclusively responsible for the code, behavior, legality, and consequences of their Applications, Tools, and external integrations.
• Limitation of Platform Liability: Stellr, LLC is not liable for any damages, data breaches, or legal infractions resulting from the misuse of our SDKs or APIs by a Developer outside of our direct marketplace governance.
• Indemnification: Developers agree to indemnify and hold Stellr, LLC harmless against any claims, lawsuits, or regulatory actions arising from the Developer's violation of this Agreement, privacy laws, or third-party intellectual property rights.
• Platform Integrity: Stellr retains full, unmitigated authority over platform architecture, uptime, feature availability, and ecosystem enforcement. We do not guarantee continuous, uninterrupted access to APIs and are not liable for business losses resulting from platform downtime or feature deprecation.