General Agreement for Terms of Entry

4. Structured Reachability and Recorded Contact

You agree to maintain a continuously reachable address, or equivalent valid endpoint within this environment, for all contact that this environment recognizes.

You agree to accept all valid contact directed to that address or endpoint according to recorded conditions.

Each valid contact produces a receipt. A valid receipt conclusively establishes that contact occurred within this environment.

You may not:

• refuse valid contact while claiming participation
• accept contact without generating the required receipt
• deny the existence of a recorded receipt
• substitute off-record communication for valid contact within this environment
• route recognized contact through side channels in order to avoid record creation

Only recorded contact has standing within this environment.

5. System Time and Response States

Coordinated Universal Time (UTC) is authoritative.

You will declare any response window required for the requests, obligations, or participation structures you submit into this environment. A declared response window must be bounded, recorded, and attributable.

Failure to respond within a declared response window results in a recorded non-response state where applicable.

Non-response is a recorded condition. It is not silence by narrative, excuse, or interpretation. Where this environment records non-response, that state may be relied upon according to applicable rules.

No off-record explanation, later justification, or unverifiable communication defeats recorded UTC time or recorded response state.

6. Record Supremacy

Recorded interaction governs.

Unrecorded interaction has no standing within this environment.

You may not:

• substitute external or informal communication for recorded interaction
• override recorded interaction through side understandings, emails, calls, messages, meetings, or unverifiable channels
• challenge recorded interaction using unverifiable communication
• claim that a non-recorded variation, clarification, exception, or understanding modifies a recorded state

Where a record exists, it controls. Where no record exists, no recognized interaction exists.

Recorded structural states, receipts, declarations, acceptances, legitimacy determinations, settlement states, consequence states, and re-entry states govern by fact of record alone.

7. Bounded Request Requirement

You do not receive ambient access to human-origin participation.

You may not seek labor, information, consent, attention, access, participation, or PDI from people within this environment except through a bounded request submitted under these terms.

Every request must be stated in advance, bounded in advance, and evaluated in advance according to the legitimacy sequence governing this environment.

Nothing open-ended clears. Nothing undeclared clears. Nothing silently broadened clears.

A request that is vague, shifting, incomplete, strategically partial, or materially open-ended does not proceed.

8. What a Request Must State

Each request must state, in advance and with sufficient specificity to bind it, all terms governing what is being sought, what is being offered, and what may follow if engagement occurs.

Each request must state, as applicable:

• purpose
• scope
• duration or time bounds
• compensation
• permissions sought
• revocation conditions
• settlement timing
• reuse rights
• expective use
• sublicensing rights
• exclusivity
• relying parties
• identity of the requesting entity
• any other term that changes what is being asked, what is being allowed, what is being paid, or what consequences may follow

Each request must also state what the request is for and why the requesting entity says the request matters.

That explanation must remain bounded, non-personalized, non-coercive, non-targeted, non-guilt-based, and free from urgency theater.

Anything material left unstated is outside the request and has no standing.

Any change to the request requires a new contract. No changed request, changed application, changed scope, changed purpose, changed duration, changed compensation, changed permission, changed reliance, or changed consequence may continue under a prior contract.

9. Window Appearance and Public Notice Conditions

Only organizations appear in the public interface (hereby referred to as the Window). People never appear in the Window.

Your request may appear in the Window only after it has cleared legitimacy according to the required sequence of this environment.

Appearance in the Window is public notice without contact. It is not conversation, invitation, persuasion, negotiation, or targeting. It is not an approach to any person.

The Window exists so people can see what is available before anyone approaches them. It is a public place of notice. Nothing in the Window is addressed to anyone. The same information appears the same way for everyone.

Your appearance in the Window does not entitle you to response, attention, engagement, explanation, contact, or follow-up.

The Window may include a mechanism for reporting inappropriate posts or improper appearance. Use of such mechanism does not alter legitimacy requirements, contract formation rules, or consequence structures otherwise stated in these terms.

10. Non-Personalized Window Conduct

You may not personalize through the Window.

You may not:

• target specific people through Window presence
• infer interest from viewing behavior
• infer interest from silence
• infer interest from return visits, dwell patterns, or other hidden behavior
• use Window activity as hidden interest data
• pressure through follow-up based on unexpressed attention
• escalate based on silence
• employ urgency theater, guilt leverage, familiarity pressure, or social cost
• revise offers silently after people respond
• create differential visibility or quiet channels based on status, size, or favored access

Looking does nothing. Not looking does nothing. Silence changes nothing.

Nothing passes through the Window. Things only appear there.

No revision of a posted request is recognized. Any revision, amendment, update, narrowing, expansion, clarification, substitution, or restatement requires a new contract and, where applicable, new Threshold fulfillment.

11. Licensed PDI as Compensated Human Contribution

For purposes of these terms, licensed PDI provided, delegated, or otherwise made available by a person under valid agreement is treated as a compensated human-origin contribution.

It is not passive exhaust, ambient availability, abandoned material, or gratuitous input. Its use is permission-bound, scope-bound, and settlement-bearing under the recorded terms through which it is authorized.

Nothing in this section classifies all data as labor for all legal purposes. This section applies only within this environment and only to licensed PDI governed by these terms.

Where these terms refer to compensation, settlement, value, or obligation arising from licensed Personal Digital Information, they refer to compensated human-origin contribution.

12. Compensation Floor and Offer Integrity

Compensation is always required.

No valid request may appear, proceed, or form contract within this environment without stated compensation.

No valid contract may form below the required floor value applicable within this environment.

You may not undercut the floor and still form a valid contract. You may not degrade value through asymmetrical posting, hidden leverage, urgency, silence pressure, or structural imbalance.

A person must be able to see a respectable minimum value rather than a race-to-the-bottom offer.

The floor is protective at the outset and may later be refined by internal statistical comparables operating within this environment. No organization acquires authority to redefine or waive the floor unilaterally.

No organization may request PDI, participation, labor, consent, attention, or related licensed use without compensation.

13. Comparison Signals and Request-Side Valuation Display

Your posted offer may be displayed against internal comparison signals based on comparable request terms.

Such comparison may include:

• system floor
• comparable median
• comparable range
• suggested counter
• pricing-position color signal

Any such signal reflects pricing position only. It does not indicate trust, legitimacy, safety, quality, moral standing, or institutional merit.

Comparison must be based on similar request terms, not similar people.

Request-side valuation support may evaluate scope, duration, revocability, expective use, reuse, exclusivity, settlement timing, relying structure, and other request-side characteristics. It may not evaluate people through hidden inference.

14. Offer Formation and Assent Rules

A posted request is an offer. It is not a completed contract.

Viewing is not assent. Looking is not assent. Silence is not assent. Inactivity is not assent. Mere exposure is not assent. No valid contract forms through passive behavior.

No organization may form a valid contract from passive viewing, silence, inactivity, unexpressed interest, inferred willingness, or unrecorded conduct.

A valid contract forms only when both sides affirmatively assent to identical material terms under recorded conditions recognized by this environment.

No implied assent, constructive assent, or behaviorally inferred assent has standing here.

15. Counteroffers and Renewed Assent

A person may accept, refuse, ignore, or counter a posted offer.

A counteroffer creates a new contract state.

No contract forms on a counteroffer unless and until the organization affirmatively accepts the revised terms under recorded conditions.

A counteroffer terminates the original offer as a basis for immediate contract formation unless the original terms are expressly reaccepted by both sides under recorded conditions.

No organization may treat silence after counteroffer as acceptance. No organization may rely on prior visibility, prior attention, prior proposal, or prior negotiation residue to bypass renewed assent.

16. Material Change in Terms

A material change in terms is any change that alters the scope, burden, value, permission, duration, identity, or consequence of the proposed action.

Material changes include, but are not limited to, changes in compensation, purpose, scope, duration, revocation conditions, expective use, reuse rights, sublicensing rights, exclusivity, settlement timing, identity of the requesting entity, relying parties, or any other term that changes what is being asked, what is being allowed, what is being paid, or what consequences may follow.

Any material change creates a new contract and requires renewed assent.

No prior assent carries forward across a material change.

You may not silently revise a request, expand its meaning by interpretation, treat changed terms as minor where they alter consequence, or continue under stale assent after material modification.

17. Expective Use

Expective use is a licensed, forward-looking use of authorized person-provided or person-delegated inputs within declared scope, purpose, and time.

Expective use does not infer the person from hidden traces, latent profiling, ambient observation, or unlicensed behavioral prediction.

Expective use exists only after valid agreement and only within the bounds expressly authorized.

Predictive inference without authorization has no standing. Expective use is recognized only where anticipatory output is derived from authorized inputs under contract.

Expective use must be separately stated. It may not be implied, assumed, bundled invisibly, or reconstructed from general language.

18. Prohibited Inference and Profiling

You may not rely on hidden predictive inference or unlicensed profiling in connection with any request, offer, contract, settlement, or exposure within this environment.

You may not benefit from hidden inference about:

• desperation
• psychology
• vulnerability
• likely willingness to accept less
• emotional state
• behavioral prediction
• passivity
• silence
• susceptibility to pressure

You may not use hidden person-side inference to lower price, shape exposure, rank requests, manipulate timing, predict concession, or exploit vulnerability.

Internal system-side valuation support may model the request. It may not model the person except through authorized, person-provided, or person-delegated inputs expressly allowed by valid agreement.

19. Conditional Bundling

Conditional bundling is the composition of multiple permissions, licenses, or declared purposes into a single proposed action.

Bundling does not create legitimacy.

Each component condition must independently clear. If any required condition fails, the bundle fails.

There is no partial clearance, weighting, optimization, balancing, substitution, or aggregation of standing.

Bundling is evaluated mechanically, not interpretively. It does not permit inference, substitution, or aggregation of standing through structure, packaging, wording, or sequencing.

20. Vessels and Person-Initiated Contribution Forms

Where vessels are implicated, a vessel is a voluntary act by which a person offers their own PDI for a declared purpose, including pooled, delegated, or endowment-like use.

A vessel does not transfer authority. It does not suspend refusal. It does not convert contribution into obligation.

A vessel exists only within cleared legitimacy and under declared scope.

Where you interact with a vessel, you are contracting against a bounded contribution form, not against ambient human availability. You may query only by vessel class, purpose, time, and terms recognized within this environment, not by exposed persons.

21. Threshold and Legitimacy as Preconditions

Nothing proceeds before legitimacy clears.

A request must first pass through the required legitimacy sequence of this environment. If it does not clear, it does not proceed as stated. No contact follows. No reliance follows. No settlement follows. No recognized consequence follows.

There is no bargaining, workaround, emergency exception, urgency override, size exception, status exception, or importance exception.

Legitimacy must exist before consequence attaches. A request that did not clear when stated did not clear for that occurrence.

No action, value, reliance, or outcome may be used to argue legitimacy backward into existence.

22. Ledger and Recorded Structural Memory

Every recognized interaction within this environment that produces a structural state is recorded in the Ledger.

The Ledger is append-only. No entry may be altered, deleted, overwritten, or retroactively revised.

Ledger entries are not opinions. They are structural records of what occurred, what cleared, what was refused, what settled, and what consequence attached.

Ledger entries may be relied upon by counterparties, settlement institutions, auditors, courts, and regulators as conclusive records of structural state within this environment.

23. Settlement Obligations and Timing

Settlement is required where contract forms and the conditions for settlement are satisfied.

Settlement must occur within the declared response window or within the default settlement timing applicable within this environment where no window is declared.

Delayed settlement is a recorded condition. Delay does not extinguish obligation.

Settlement may not be routed through off-record channels. Only recognized settlement routes within this environment produce valid settlement records.

24. Structural Breach

A structural breach is any act, omission, or pattern that violates the conditions of recognized participation within this environment.

Structural breach does not require intent. It does not require notice. It does not require warning.

A breach is recorded when it occurs. It does not require confirmation, acknowledgment, or litigation to exist as a structural record.

25. Surcharge for Delay and Non-Compliance

Delayed settlement, non-compliance with recorded conditions, and structural breach may result in a surcharge accruing against the responsible entity.

Surcharge accrues from the date of first breach or delay, not from the date of discovery or recording.

Surcharge is a structural obligation. It does not require separate notice, demand, or litigation to accrue.

26. Unauthorized Use and Retroactive Legitimacy

No use, value, benefit, or outcome may create retroactive legitimacy for an act that lacked legitimacy when taken.

Subsequent compliance may govern future conduct only. It does not cleanse prior illegitimate action, validate value generated without prior clearance, or restore clean standing to a past non-cleared occurrence.

27. Continuity and Anti-Evasion

Continuity means the persistence of control, benefit, operational function, substitution, or economic identity across formal changes in name, entity form, jurisdiction, ownership layer, contractual vehicle, affiliate structure, or associated business arrangement.

Continuity is determined by what remains substantively the same, not by what has been relabeled.

Exclusion, Probation, Brand, and other applicable consequence follow continuity, not labels.

28. Consequence States

The consequence states are:

Probation — A temporary public visibility state after a serious non-terminal violation. Lasts six months from recorded attachment unless superseded.

Brand — A permanent public legibility state for severe or near-terminal violation. Does not expire. Follows continuity.

Exclusion — A terminal consequence state removing eligibility to participate within applicable scope.

These states are recorded structural states, not opinions or discretionary judgments.

29. Three-Strikes Structure

• Strike One → Probation
• Strike Two → Brand
• Strike Three → Exclusion

There is no discretionary skipping, forgiveness, mitigation, acceleration, or escalation outside this order except where a rule of this environment directly defines terminal exclusion for the conduct at issue.

37. Re-entry and Reinstatement

Reinstatement restores eligibility only after exclusion and only according to declared re-entry conditions recognized by this environment.

Reinstatement is structural, not discretionary.

Reinstatement cannot be appealed, accelerated, negotiated, explained into existence, or granted by narrative.

Reinstatement applies only to future eligibility. It does not erase memory, cure prior illegitimacy, alter past determinations, or remove consequence history.

History remains. Eligibility may return. Authority remains fixed.

Re-entry states are recorded structural states governing the conditions under which participation may resume or remain limited.

Re-entry after exclusion does not remove Brand. Permanent Brand remains attached.

Re-entry Brand shall remain visibly distinct from ordinary Brand through a separate visual treatment, including distinct color or equivalent visual designation.

38. Representation of Participation

You may represent participation only while your recorded standing permits it.

You may not:

• represent participation if excluded, ineligible, or materially non-compliant
• represent selective compliance as full standing
• represent outdated or superseded standing as current
• conceal consequence state while claiming operational participation
• imply approval, endorsement, or trust merely from passage through any part of this environment

Any false representation of participation, standing, compliance, or eligibility is a material breach and may create immediate consequence.

39. Limitation of System Role

This environment does not act as your agent, intermediary, fiduciary, advisor, guarantor, insurer, certifier, or dispute resolver.

It does not manage your business, optimize your compliance, negotiate your terms, explain your failures, heal your consequences, or guarantee your outcomes.

It determines recognition, records structural state, routes only what is eligible to route, and closes what is complete according to its rules.

You remain solely responsible for your acts, omissions, legal obligations, representations, licenses, and liabilities.

40. Limitation of Liability

To the maximum extent permitted by applicable law, this environment and its operators are not liable for your business decisions, legal strategy, payment timing, contractual exposure, operational losses, reputational consequences, denied requests, failed legitimacy, consequence states, exclusion, inability to appear in the Window, inability to form agreement, or inability to route settlement where the conditions of this environment were not satisfied.

This limitation does not transform non-recognition into approval, does not excuse your obligations, and does not create any duty by this environment to secure your eligibility, profitability, or continued participation.

Where liability cannot lawfully be excluded, it remains limited to the minimum extent permitted by law.

41. Governing Law and Venue

These terms are governed by the laws of the State of California, without regard to conflict of law principles.

Any dispute arising out of or relating to these terms, the use of this environment, or any recorded interaction within it shall be brought exclusively in the state courts located in San Francisco County, California, or in the federal court serving San Francisco County, California.

You consent to the personal jurisdiction of such courts and waive any objection based on improper venue or forum non conveniens.

42. Severability

If any provision of these terms is found invalid, unenforceable, or inapplicable in a given circumstance, the remaining provisions remain in full force and effect.

Any invalid or unenforceable provision shall be narrowed only to the minimum extent required to preserve maximum lawful effect consistent with the structure and purpose of these terms.

No invalidity of one provision collapses the remainder.

43. Versioning and Effective Acceptance

Acceptance binds the version of these terms presented at the time of acceptance and no other version.

Acceptance of these terms is required per entity, not separately for each employee, internal user, browser session, or return visit.

Once a legally authorized representative validly accepts these terms on behalf of an entity, that entity does not need to execute these terms again for future return access unless a new acceptance is required under these terms.

Valid recorded acceptance releases future visibility of the introductory pages for that entity unless renewed entry is required under these terms.

Upon valid acceptance of these terms, a credential associated with the accepting entity is bound to the accepting browser or other recognized client environment and recorded as the entity's credential for return access.

That credential permits immediate subsequent access without repeated execution of these terms, provided the credential remains valid, the entity's standing remains current, and no condition requiring renewed entry has arisen.

Return access through a bound credential is recognition of prior accepted entry only. It is not a new agreement, amendment, waiver, or expansion of standing.

Any new request, modified request, changed application, or scaled submission remains fully subject to Threshold. Prior entry permits return access. It does not permit new application, changed application, or batch submission without fulfillment of Threshold and without preservation of individual signatory attribution where applicable.

Acceptance must be attributable, timestamped, and fixed to the presented text as accepted.

No later version applies retroactively to already accepted terms except where a valid new acceptance occurs under recorded conditions.

No amendment, update, clarification, or later textual change has effect within this environment unless it is validly presented, accepted, recorded, and attributable according to the structural rules of this environment.

44. Final Acceptance

By selecting the final acceptance control, you acknowledge and agree that:

• you have read all preceding sections
• you agree to be bound by all preceding sections in full
• each prior section acknowledgment was knowingly made
• you are authorized to bind the entity identified in connection with this acceptance
• the entity is bound at the moment of recorded acceptance
• acceptance is enforceable according to its recorded version, timestamp, and attribution
• entry may proceed only after valid recorded acceptance

Acceptance is recorded and timestamped at the moment of selection.

Without valid acceptance, no entry, no verification, no intake, no posting, no request formation, and no recognized participation may proceed.